Re: HTTP/1.1 draft 12 aug 1996 and content encodings

> This seems like a protocol design error, and doesn't really match
> HTTP/1.0 practice. No "Accept-encoding" header means that the server
> guesses what's acceptable to the client; the "MAY assume" is nonsense,
> since in fact, if the server knows some novel, new encodings, it's
> certain that there are clients that don't send Accept-encoding and yet
> don't know about them.

"guessing" and "MAY assume" are identical terms.


 ...Roy T. Fielding
    Department of Information & Computer Science    (fielding@ics.uci.edu)
    University of California, Irvine, CA 92697-3425    fax:+1(714)824-4056
    http://www.ics.uci.edu/~fielding/

Received on Saturday, 14 September 1996 21:36:38 UTC