Re: RevalidateCacheEntry merges headers from cache which do not exist any more

2023-11-08 Thread Sneha Murganoor
I misinterpreted the HTTP protocol. In this case, the server's decision to return a 304 status code was incorrect because there was a change in the metadata, even though there was no change in the payload. Just to clarify, does this mean that when there is a change in either the payload or

Re: RevalidateCacheEntry merges headers from cache which do not exist any more

2023-11-08 Thread Oleg Kalnichevski
On 08/11/2023 15:58, Sneha Murganoor wrote: Thanks for the reply. Yes we understand that when an entry in cache is stale, we make conditional get requests. We are wondering if there is way we dont make conditional get instead just make unconditional get call, since AWS S3 returns as 304 status

Re: RevalidateCacheEntry merges headers from cache which do not exist any more

2023-11-08 Thread Sneha Murganoor
Thanks for the reply. Yes we understand that when an entry in cache is stale, we make conditional get requests. We are wondering if there is way we dont make conditional get instead just make unconditional get call, since AWS S3 returns as 304 status code even when there is header removed from the