Ask HN: Why does Deno Deploy block /wp-content?

For a website, which I once migrated from WordPress to Deno Deploy, I have a simple redirect in place for any files below /wp-content/. Today I discovered that this redirect does not work anymore. After several hours of searching for a bug in my own code or configuration, I finally found the culprit: Deno Deploy itself is handling this URL differently!

Take a look at https://deno.com/wp-content - unsurprisingly it will yield a 404. However, https://deno.com/should-not-exist will yield a different 404. The same applies for https://usefresh.dev/wp-content and presumably for any other website hosted on Deno Deploy. Really strange...

Does anybody have an idea, why or when this bug might have been introduced?