You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 18, 2024. It is now read-only.
I worked around this issue on my end by serving HEAD requests like GET within CF. (which is technically ok but really not ideal).
but yeah, I was having issues with HEAD requests being uncached, which ends up akin to being DDoSed by web crawlers... Figured I'd bring it up here. :)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Since bots often use HEADs to check for content updates or if the server is alive, it makes sense to cache HEADs via CDN.
With this same reasoning, I think the upper process should attach the cache headers to both GETs and HEADs.
The text was updated successfully, but these errors were encountered: