Hi, I’m seeing some unexpected behavior when it comes to the caching of HEAD requests. GETs for the same URL come back cached every time as expected, but HEADs will occasionally come back with a MISS. We’re using shielding and it really only seems to occur whenever we end up going to a shield node directly. I’m logging the
fastly_info.state variable and the misses come back as just plain
MISS values, while the hits are always
HIT-CLUSTER. Is there something different in the way that HEAD requests vs GET requests are cached that might be causing this?
Please sign in to leave a comment.