Welcome! Log In Create A New Profile

Advanced

Re: How to disable/not to send Last-Modified Header

Maxim Dounin
January 13, 2011 08:28AM
Hello!

On Wed, Jan 12, 2011 at 04:12:14PM -0500, bartzy wrote:

> Sorry for the bump, but this didn't fix the issue in my case.
>
> I have static files that never change. I want to set future expires
> header for them and to force the browser NOT to check if the cached
> version is valid with if-modified-since conditional GET.

Short answer: you can't.

Long answer: browsers do whatever they want and can't be forced to
not check cached resource. Most of the checks may be avoided with
"expires max;" directive, but not all.

> when I remove the Last-Modified header in nginx like Igor suggested,
> Only the expires and cache-control (max-age...) get sent, but I think
> the browser doesn't even save the resource in cache (tried with both IE8
> and FF3.6).

Igor never suggested to remove Last-Modified header, he just
answered how to do it. It's thread starter who thinks this will
help.

Maxim Dounin

_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx
Subject Author Posted

How to disable/not to send Last-Modified Header

tunggad March 11, 2010 12:08PM

Re: How to disable/not to send Last-Modified Header

Igor Sysoev March 11, 2010 04:04PM

Re: How to disable/not to send Last-Modified Header

tunggad March 13, 2010 04:41PM

Re: How to disable/not to send Last-Modified Header

bartzy January 12, 2011 04:12PM

Re: How to disable/not to send Last-Modified Header

Maxim Dounin January 13, 2011 08:28AM

Re: How to disable/not to send Last-Modified Header

bartzy January 14, 2011 07:06PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 305
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready