Re: Content-Encoding confusion -Reply -Forwarded

Daniel said
>> One possible solution would be for the server to include a
>>  content-disposition:  response header; as in
>>       Content-Disposition: attachment; filename="html40.pdf"

Henrik replied
>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.

Perhaps I'm reading the problem wrong, but it seems that when the client
saves the file to disk, the default name is whatever.pdf.gz; a name that
acrobat doesn't like (acrobat wants to see .pdf).  And though it's not
complicated to retype the name, a lot of people fail to do this. Hence,
the need to control the default "save as" name.


-----------------------------------------------------------
danielh@crossslink.net
-----------------------------------------------------------

Received on Wednesday, 3 May 2000 00:45:33 UTC