On 14.04.2010 20:57, Tyler Close wrote:
... Alternatively, instead of drawing the line at the HTTP spec, we could draw it based on functionality. The following list includes all end-to-end response entity headers, as well as all headers used for caching and redirection: ...
Well, it does not; there's a header registry for that, for instance, what about "Content-Range"?
It also excludes all headers that will be defined in the future. Best regards, Julian
