Re: Content-Encoding confusion -Reply

> 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


Received on Tuesday, 2 May 2000 19:31:23 UTC