[11605] in www-talk@info.cern.ch
Re: Content-Encoding confusion -Reply
daemon@ATHENA.MIT.EDU (Henrik Frystyk Nielsen)
Tue May 2 19:39:34 2000
Message-Id: <000901bfb48e$74898af0$c2bb1eac@redmond.corp.microsoft.com>
Reply-To: "Henrik Frystyk Nielsen" <frystyk@microsoft.com>
From: "Henrik Frystyk Nielsen" <frystyk@microsoft.com>
To: "Daniel Hellerstein" <DANIELH@ers.usda.gov>, <www-talk@w3.org>
Date: Tue, 2 May 2000 16:30:38 -0700
Mime-Version: 1.0
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: 7bit
Resent-From: www-talk@w3.org
> One possible solution would be for the server to include a
> content-disposition: response header; as in
> Content-Disposition: attachment; filename="html40.pdf"
Content-Disposition actually has no impact on this at all. It is still
the Content-* header fields that describe the encoding, type, etc. of
the entity body so a client is no better off using the value of a
Content-Disposition header field instead of the URI for the same
reasons.
Henrik
