New issue
Advanced search Search tips

Issue 650117 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Compat



Sign in to add a comment

We might want to work around sites that send a bad Last-Modified header

Project Member Reported by agl@chromium.org, Sep 26 2016

Issue description

(This is forwarded from Yngve N. Pettersen at his request. I don't know whether this server issue should be our problem, personally.)

https://popehat.com, incorrectly, perhaps based on some issue in its scripting or file update system, sends this response header:

  Last-Modified: Thu, 01 Jan 1970 00:00:00 GMT

Which of course results in the chromium network code sending

  If-Modified-Since: Thu, 01 Jan 1970 00:00:00 GMT

Since the server believes that everything was modified at the epoch, it mightn't send an updated document.

I would suggest that at least any date as old as that should be ignored, and the header should be ignored. It's been a long time, so I am no longer confident I remember correctly, but I seem to recall that I added such code in the old Opera code.

Another item is that I am actually seeing this header being sent for full reload (F5) requests, too, when the "Cache-Control:max-age=0" header is sent. Sending If Modified since in a reload request is IMO not just unnecessary, but I wouldn't be surprised if there are misconfigured/buggy servers that might prefer the that header to the the cache control header. Perhaps it might be better to avoid such potential for confusion?

 

Comment 1 by mmenke@chromium.org, Sep 26 2016

Cc: mmenke@chromium.org
In general, I think we should be very careful about working around server bugs, beyond making sure we don't do something too crazy (Like crashing, or having our security checks break down, etc).  So I don't think we should add a hack for this specific case.
Project Member

Comment 2 by sheriffbot@chromium.org, Sep 26 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 3 by agl@chromium.org, Sep 26 2017

Status: WontFix (was: Untriaged)

Sign in to add a comment