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

> 1. > GET index.html.gz
>    < Content-type: text/html
>    < Content-encoding: gzip
> 
>    This is _only_ usefull for simple decoding in the client.  But it
>    requires knowledge of filename conventions if you want to determine
>    if the server has done content negociation or not, and wether to
>    save the document encoded or decoded to disk, in a automated
>    manner.

Filename conventions are irrelevant in HTTP.  In order for your application
to work correctly, it must obey the same constraints as any cache.
That means the client must map URLs to responses, not filenames.
How the application stores things locally is application-dependent, but
there are sufficient clues given by Content-Location and Vary such
that it can indeed know whether or not negotiation was used.


 ...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 Monday, 16 September 1996 02:28:01 UTC