Project

General

Profile

Actions
Copy link

Bug #392

closed

support for if-unmodified-since unless-modified-since

Added by Anonymous almost 19 years ago. Updated over 17 years ago.

Status:
Fixed
Priority:
Normal
Category:
core
Target version:
1.4.9
ASK QUESTIONS IN Forums:

Description


if-unmodified-since: http standard, see rfc2616.txt
unless-modified-since: ie proprietary

the problem:
1. request to a.jpg, but make sure to download Partially
2. touch a.jpg in server
3. re-request, ie send with range+unless-modified-since, other browser should send range+if-unmodified-since i guess.

expected: lighttpd response 412 Precondition Failed
actual: lighttpd response 206 Partial Content

-- xuefer

Actions
Copy link
 #1

Updated by Anonymous almost 19 years ago

sorry, expected: 200 OK

-- xuefer

Actions
Copy link
 #2

Updated by Anonymous almost 19 years ago

the real problem is
if u, instead, do
1. same
2. update a.jpg with other content.
3. same
your browser get a corrupted image. and it's "nicely" cached in client.
4. F5 (not ctrl+F5), re-request, got "not modified". too bad, the client will still see a big red cross X, most user don't know what there is CTRL+F5

particularly, i was checking lighttpd.rrd+images from lighttpd+browser.

-- xuefer

Actions
Copy link
 #3

Updated by jan almost 19 years ago

  • Status changed from New to Fixed
  • Resolution set to fixed

in 1.4.9 we will have support for If-Range which is used by at least FF if ETags are sent.

Actions
Copy link

Also available in: Atom