Different store to cache strategies about guzzle-cache-middleware HOT 6 CLOSED

Hi, I see what you mean. But this will break the RFC.

[...] the cache MUST:
[...]
   o  use other header fields provided in the 304 (Not Modified)
      response to replace all instances of the corresponding header
      fields in the stored response.

http://tools.ietf.org/html/rfc7234#section-4.3.4

I understand, that a server can (by the way of a 304) replace one or more headers in the cached response. So, it's not "really useless" in general.

Maybe, we can do a different method in CacheStrategyInterface like update(RequestInterface $request, ResponseInterface $response). With that, you can extend the strategy and change the behavior of this method.

Is it a performance issue for you?

from guzzle-cache-middleware.

Yes, additional method will help as well.

from guzzle-cache-middleware.

In my case Etag = md5(content) so it is really meaningless to update the cache per each request.. Frontend is a WP site, so yes, it's a performance issue for me ))

from guzzle-cache-middleware.

Ok, I will try to look at this today or tomorrow. Thank for reporting this issue!

from guzzle-cache-middleware.

@vicmosin Can you check #52? Is it useful for you like that?

from guzzle-cache-middleware.

Fixed with v1.3.

from guzzle-cache-middleware.