[11600] in www-talk@info.cern.ch
Re: Content-Encoding confusion
daemon@ATHENA.MIT.EDU (Henrik Frystyk Nielsen)
Tue May 2 17:34:48 2000
Message-Id: <002801bfb47c$e02cccc0$6db91eac@redmond.corp.microsoft.com>
Reply-To: "Henrik Frystyk Nielsen" <frystyk@microsoft.com>
From: "Henrik Frystyk Nielsen" <frystyk@microsoft.com>
To: "Hugo Haas" <hugo@w3.org>, <www-talk@w3.org>
Date: Tue, 2 May 2000 14:24:57 -0700
Mime-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Resent-From: www-talk@w3.org
> When I request html40.pdf, it is obvious that my browser needs to
decode
> (i.e. uncompress) the file on the fly, and save it under html40.pdf.
The problem is that when you save a file locally you can't use the
Content-* header fields directly but instead have to express the
bindings using file suffixes. However, a URI is opaque so the client
makes a mistake by taking the last part of the URI as a file name. The
reason is that there is no guarantee that the server and the client has
the same bindings between file name suffixes and media types or that all
suffixes are included in the URI.
The only way to make this work is if the client uses the Content-*
header fields to generate a proper set of suffizes that has the right
binding the local machine and give the local file a name with these
suffixes.
Henrik Frystyk Nielsen,
mailto:frystyk@microsoft.com
