[✨] Automatic simple 404 responses for file requests about qwik HOT 9 OPEN

where are you deploying qwik to?

from qwik.

looks like google cloud run if you deploy all built files in /build into the same bucket location behind a cdn then this will also fix the problem. in the ssr.entry you can set base to that bucket url

so

base: "https://my-cdn.com/my-path-to-bucket/build/"

from qwik.

not quite sure I'm understanding you :) Everything works as expected, files do exist and are pulled correctly. Our problem (and probably everyone's problem) is that if you make a request for a non-existing JS file (maybe due to caching) that it delivers the 300kb custom JS file instead of a few bytes:

• www.myapp.com/build/q-some-old-non-existent-file.js - 300kb to tell the browser it doesn't exist

The ethos of qwik is that everything is fast and optimised out of the box and developers don't accidentally fall into performance pitfalls, so delivering your custom 300kb 404 page and causing 30mb of wasteful requests is something that developers have to understand and manually fix.

from qwik.

ok the solution was setting cloudflare (that is in front of cloud-run) anything with /build to be cache forever

from qwik.

@PatrickJS although it wouldn't hurt to have the static file serving for the assets base serve simple 404s

from qwik.

yup I agree

from qwik.

I have a draft PR here if anyone wants to take over the PR.

Basically remake it and check that everything works. Possible add a test
#6307

from qwik.