Am currently trying

_middleware.js

stuff for the first time with CF Pages, in an attempt to use it instead of an existing CF Worker. The middleware works perfectly on the

pages.dev

version — but, on the custom-domain version from that

pages.dev

, only the HTML files are affected even though it’s for all routes and files. To be more specific: on the

pages.dev

version, a number of custom headers (such as for caching) are added to a variety of file types, including CSS and image files; but, on the custom-domain version, this works for only the HTML files. Is there something special I have to do in the domain’s DNS, or elsewhere, to make the middleware work properly on the custom domain, too? (And I did remove the custom domain’s routes from the Worker for the test, so the Worker shouldn’t have been interfering.) The

pages.dev

domain = static-site-2to.pages.dev The custom domain = brycewray.com **Note**: I have had to re-add the custom domain routes to the Worker and take the

_middleware.js

file out of the project in order to regain the previous functionality, at least until I can learn why the middleware file doesn’t work on the custom domain. Let me know if you want me to restore the test setup.

Sounds like the custom domain is maybe doing some caching in front of the asset requests?

Thanks for replying! I checked the domain caching settings. Caching Level is set to Standard and Browser Cache TTL is set to Respect Existing Headers. This combination has always worked properly with my Worker, so I guess I thought the same would be true for the middleware, given that it's really a Worker behind the scenes and is adjusting the same assets’ settings. Also, it wasn’t just that custom caching was ignored. There were other headers in the middleware (some just for testing purposes), and none was attached to the non-HTML files under the custom domain. 🤔 . . . Or should I perform a Purge Everything under Purge Cache before trying the middleware again? Just not sure how to proceed.

Hey, thanks for doing that testing. I’m afk right now, try disabling caching entirely. If there’s no setting for that on the Caching Configuration section, there might be a Page Rule you can apply? I suspect that this is going to become our recommended set up as more and more people get into full-stack apps, but we definitely need to do a deeper investigation into all the complexities and trade-offs here.

Did briefly disable caching through one of the (beta) Cache Rules, but still saw same need to toggle Warp off/on to see middleware changes even after hard-reload-and-refresh cycles on multiple browsers/devices. Seems to be 95% Warp and 5% CF caching (if that). Have now restored CF caching and reported this as a (possible) Warp bug. Weird that it doesn’t seem to affect CFP sites without the custom domains, but... 🤷‍♂️ Anyway, I will tag this with “Solved.” Thanks.