On Thu, Jul 25, 2019 at 12:02:27PM +, Andrew Andonopoulos wrote:
Hi there,
> Nginx decide which content to cache based on the configuration under
> "Location" + the cache key? For example I have proxy_cache which means will
> cache everything which match the specific location?
>
nginx cac
To: nginx@nginx.org
Subject: Re: Nginx cache-control headers issue
On Sat, Jul 20, 2019 at 10:10:39AM +, Andrew Andonopoulos wrote:
Hi there,
> Also, I want to ask you, I saw that the last-modified header with token is
> always: Last-Modified: Sun, 19 Nov 2000 08:52:00 GMT, but there is
On Sat, Jul 20, 2019 at 10:10:39AM +, Andrew Andonopoulos wrote:
Hi there,
> Also, I want to ask you, I saw that the last-modified header with token is
> always: Last-Modified: Sun, 19 Nov 2000 08:52:00 GMT, but there isn't line
> in the config forcing this date/time.
> Can you suggest whi
the config forcing this date/time.
Can you suggest which code forcing this modified time?
Thanks
Andrew
From: nginx on behalf of Francis Daly
Sent: Saturday, July 20, 2019 7:38 AM
To: nginx@nginx.org
Subject: Re: Nginx cache-control headers issue
On Sat, J
On Sat, Jul 20, 2019 at 12:33:24AM +, Andrew Andonopoulos wrote:
Hi there,
> I checked multiple scenarios and when I removed the token I got the correct
> header. Looks like when the token is active, I am getting wrong headers.
There is lots going on in your config.
I suggest it may be use
ader Cache-Control;
proxy_ignore_headers Cache-Control;
Thanks
Andrew
From: nginx on behalf of Andrew Andonopoulos
Sent: Saturday, July 20, 2019 12:33 AM
To: nginx@nginx.org
Subject: Re: Nginx cache-control headers issue
Hi Francis,
Thanks for t
ly 19, 2019 10:47 PM
To: nginx@nginx.org
Subject: Re: Nginx cache-control headers issue
On Thu, Jul 18, 2019 at 06:44:13PM -0400, andregr-jp wrote:
Hi there,
> I have an nginx proxy which suddenly adding 2 cache-control headers and the
> last modified time is always the current time:
I su
On Thu, Jul 18, 2019 at 06:44:13PM -0400, andregr-jp wrote:
Hi there,
> I have an nginx proxy which suddenly adding 2 cache-control headers and the
> last modified time is always the current time:
I suspect that whatever is being reverse-proxied changed recently to
send these headers.
>
Hello,
I have an nginx proxy which suddenly adding 2 cache-control headers and the
last modified time is always the current time:
curl -I
https://example.com/hls/5d15498d3b4e13.57348983/1280_720_3200_5d15498d3b4e13.57348983.m3u8?token=st=1563488654~exp=1563575054~acl=/hls/5d15498d3b4e13.57348983/
Hello,
I have an nginx proxy which suddenly adding 2 cache-control headers and the
last modified time is always the current time:
curl -I
https://example.com/hls/5d15498d3b4e13.57348983/1280_720_3200_5d15498d3b4e13.57348983.m3u8?token=st=1563488654~exp=1563575054~acl=/hls/5d15498d3b4e13.5734898
Hello,
I have an nginx proxy which suddenly adding 2 cache-control headers and the
last modified time is always the current time:
curl -I
https://example.com/hls/5d15498d3b4e13.57348983/1280_720_3200_5d15498d3b4e13.57348983.m3u8?token=st=1563488654~exp=1563575054~acl=/hls/5d15498d3b4e13.5734898
11 matches
Mail list logo