"Craig Sowadski" <[EMAIL PROTECTED]> writes: > 1. I can implement a patch like my original that only uses the > if-modified-since when the last-modified field is excluded from the > head-only request.
Isn't that what your most recent patch implements? > 2. Send the if-modified-since request, then get header to check for > size only if the if-modified-since request sends back a "304 - not > modified" That means introducing an additional hop for unchanged files. This is in a way even worse because I'd expect them to be in the majority. > 3. implement a separate time-stamping and file-size checking > options. This might make the most sense. Or, we could completely ignore the file size issue and simply trust what If-Modified-Since tells us. I guess I'd like for time-stamping to use If-Modified-Since, period. That's what it's for, and the Last-Modified thing has always been a weird hack that somehow survived the times. What do the others think about this?
