You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by GitBox <gi...@apache.org> on 2021/11/30 13:55:45 UTC

[GitHub] [trafficserver] fdiary commented on issue #8539: CACHE_LOOKUP_HIT_FRESH status for POST request is not good

fdiary commented on issue #8539:
URL: https://github.com/apache/trafficserver/issues/8539#issuecomment-982658571


   @SolidWallOfCode
   > does it require having done a GET previously that was cached? 
   
   Yes.
   
   Imagine we have the following chronological requests in the **same** URL : 
   
   1. GET : CACHE_LOOKUP_HIT_MISS -> fetch from the origin server, then respond it and store in cache
   2. GET : CACHE_LOOKUP_HIT_FRESH -> fetch from the cache, then respond it
   3. POST : CACHE_LOOKUP_HIT_FRESH -> but fetch from the origin server, then respond it and invalidate the existing cache
   4. POST : CACHE_LOOKUP_MISS -> fetch from the origin server, then respond and do NOT store in cache
   
   And the issue here is in 3. case above, i.e. compress plugin implementation does **not** assume "CACHE_LOOKUP_HIT_FRESH but fetch from the origin server" case.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@trafficserver.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org