Workers with Static Assets missing features

For Workers & Pages, what is the name of the domain?

example.com

What is the issue or error you’re encountering

Workers with Static Assets doesn’t currently support the _headers file that Pages offers, which is necessary for me to set HTTP response headers such as CORS and other security headers. Of course I could set the Worker to run first, but then it would be invoked for every static asset just to set some headers, and that would count toward the Worker quota (in terms of daily requests and CPU time). This prevents me from migrating from Pages as suggested in Migrate from Pages · Cloudflare Workers docs. Am I missing something? If not, I’d like to know if I can rely on Pages for the future years or if Workers with Static Assets will reach feature parity with Pages. Bonus question: I’ve been reading about Advanced Mode (Advanced mode · Cloudflare Pages docs); does using that imply that every request (including those to static assets) go through the Worker and therefore count toward the quota? Thanks in advance.

Static Asset Workers support a _headers file now (it’s very recent).

1 Like

Thank you, I had missed that part of the docs. Is there support for _redirects as well?

I’ve actually found that _redirects is supported too. Sorry for the rushed up question!

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.