Re: [freenet-dev] FProxy breaks HTTP/1.1 specs

[Tuomas Lukinmaa]

> Too many broken browsers substitute their own crap for the
> server-supplied 404.

Atleast it's known crap to the users. :) If there's some known browsers
to break badly on the handling of 404, there should be User-Agent
exception for them. It is not reasonable to make everyone suffer over a few broken browsers.

> ETag is just a string, so the base64-encoded key of the current file
> would do nicely (for key responses) and something unique-ish for the
> fproxy html/graphics.

The CHK-string of content should do nicely. It would be better to use Last-Modified for FProxy's own content to minimize the amount of processing (we don't want to calculate hashes over and over for the FProxy content).

> No, setting a reasonable Expires: time is a lot more friendly.
> Setting the Expires: header to +infinity for normal keys
> rollover-time for mapped keys seems logical.

I disagree especially when it comes to Freenet content. It might be
logical, but it is NOT correct. Correct way is to use strong validators over weak ones.

http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.3.3

> Last-modified: is important as it tells the cache how volitile the
> page is. Set it to 1-year ago since we don't really know how old
> things are.

If it's not known how old the content is, ETag should be used. It's a
strong validator in Freenet's case (CHK strings) and just made for these
situations.

http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.3.2
http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.3.4

<blockquote>
The ETag response-header field value, an entity tag, provides for an
"opaque" cache validator. This might allow more reliable validation in
situations where it is inconvenient to store modification dates, where
the one-second resolution of HTTP date values is not sufficient, or
where the origin server wishes to avoid certain paradoxes that might
arise from the use of modification dates.
</blockquote>




_______________________________________________
devl mailing list
[EMAIL PROTECTED]
http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl