Hello!
On Wed, Sep 14, 2016 at 02:19:25AM -0400, jchannon wrote:
> NGINX authors might want to read this thread. Essentially Mark is saying
> that this is a bug
> https://twitter.com/darrel_miller/status/775684549858697216
The fact that headers are not merged is one of the main reasons
why prox
NGINX authors might want to read this thread. Essentially Mark is saying
that this is a bug
https://twitter.com/darrel_miller/status/775684549858697216
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,269457,269556#msg-269556
___
nginx mailing
Hello!
On Sun, Sep 11, 2016 at 06:56:17AM -0400, jchannon wrote:
> I have nginx and its cache working as expected apart from one minor issue.
> When a request is made for the first time it hits the origin server, returns
> a 200 and nginx caches that response. If I make another request I can see
>From what I understand, 304 answers should not try to modify headers, as
the cache having made the conditional request to check the correctness of
its entry will not necessarily update it:
https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.5.
The last sentence sums it all: '*If* a cac
I have nginx and its cache working as expected apart from one minor issue.
When a request is made for the first time it hits the origin server, returns
a 200 and nginx caches that response. If I make another request I can see
from the X-Cache-Status header that the cache has been hit. When I wait a
