Inconsistency between HEAD and GET request handling

Follow
Ray Diciaccio

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?

Thanks!

  • Ray
0

Comments

3 comments

Sort by Date Votes
  • Peter Wohlers

    Hi rayd-

    Yes, we have a distributed storage architecture in our POPs and we don't cluster the HEAD requests.

    Use GET requests if you are trying to determine cacheability. i.e. something like: curl -svo /dev/null http://www.example.com

    0
    Comment actions Permalink
  • Ray Diciaccio

    Ah, thanks for the quick response and explanation peter!

    0
    Comment actions Permalink
  • Peter Wohlers

    As an update to this, HEAD requests now cluster, so these should now reflect proper behavior.

    --Peter

    0
    Comment actions Permalink

Please sign in to leave a comment.

New post