Expires header not updated when status 304

[eduardorochabr]

I've noticed that LSWS does not send Expires header in 304 responses, so the browser always uses the old Expires. Shouldn't the Expires be updated?

Use case:

1. First page visit

get /default.css
response: 200, Expires: 25-May-2007 18:00

2. Page visit before expires

(nothing, since browser cached)

3. Page visit after expires

get /default.css
response: 304, etag: '34-342342-2342'

ALL consecutives page visits make the browser request the resource again, based on old Expires.

[mistwang]

Fix will be in 3.1.2 release.

[eduardorochabr]

Great news! Thanks!

[mistwang]

Please download and try http://www.litespeedtech.com/package...6-linux.tar.gz
see if it is fixed.

[eduardorochabr]

It works, thanks!

However, I have a question. I tested with the Example virtual host, setting image expires to a short time. It worked perfectly, but I didn't get why "index.html" gets cached, do you know why? Just curious.

Will it be available via update, link 3.1.1?

Thanks once again.

[mistwang]

It is up to the browser to cache or not to cache a html page unless you have cache control header in the reply.

It will be available via update, we still need working on some features.

[eduardorochabr]

Hi mistwang,

How could I reinstall this version in production smoothly? Is there a way?

If I just reinstall it using the same values, like users and directories, it would be OK? I mena, it would use the same settings as before?

Thanks.

[mistwang]

Yes, just run the install.sh, then select "upgrade", your current configuration will not be touched.

[eduardorochabr]

Hi mistwang,

I've just upgraded a production server to this version, and the main URL of the site gets a 403, like "http://www.example.com/".

The previous version was 3.1.1-std, and when I switch back it works without problem.

Any idea?

Thank you.

[mistwang]

Do you have any request filter rule configured? Maybe turning on "Debug logging" by set "Debug Level" to "High" will help.