responses as 304 to clients even without
the If-Modified-Since header?"
What requests were triggering the 304 response?
Were you observing what a browser was seeing or were you using curl or
wget to trigger the response?
Peter
Sent from my iPhone
On Jul 26, 2017, at 5:10 AM, Ryan Ba
ant behavior and webpagetest.org
<http://webpagetest.org>
to see how different browsers handle your site.
Peter
On Jul 26, 2017, at 3:29 AM, Ryan Barclay <mailto:r...@rbftpnetworks.com>> wrote:
The following config seems to work for the situation I discussed:
proxy_cache_valid
webpagetest.org
<http://webpagetest.org>
to see how different browsers handle your site.
Peter
On Jul 26, 2017, at 3:29 AM, Ryan Barclay <mailto:r...@rbftpnetworks.com>> wrote:
The following config seems to work for the situation I discussed:
proxy_cache_valid
config or future problems
that may arise?
On 24/07/2017 16:20, Ryan Barclay wrote:
We have a pretty simple setup with NGINX sitting on the front and a
backend server (on a separate physical server) that provides the content.
Nginx then caches content based on the EXPIRES and Cache-Control
directive to disable the 304 cache explicitly.
|proxy_cache_valid 304 0;|
On 24 July 2017 at 23:20:35, Ryan Barclay (r...@rbftpnetworks.com
<mailto:r...@rbftpnetworks.com>) wrote:
We have a pretty simple setup with NGINX sitting on the front and a
backend server (on a separate physica
We have a pretty simple setup with NGINX sitting on the front and a
backend server (on a separate physical server) that provides the content.
Nginx then caches content based on the EXPIRES and Cache-Control headers
set by the origin server.
We noticed that NGINX was not issuing 304 headers to
