W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 1997

RE: Using Content-Encoding and Content-Disposition together

From: Yaron Goland <yarong@microsoft.com>
Date: Mon, 4 Aug 1997 17:50:54 -0700
Message-Id: <11352BDEEB92CF119F3F00805F14F4850354E11C@RED-44-MSG.dns.microsoft.com>
To: "'mcmanus@AppliedTheory.com'" <mcmanus@appliedtheory.com>, kweide@tezcat.com
Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/4079
I also agree that the second one is correct. We should not confuse
content-encoding with the actual file. After all I could easily be
dealing with a server where I, a server side app, send the server a
plain text file with a content-disposition of .txt and the smart server
knowing it is talking to a UA that supports compression decides to
compress on the fly.

> -----Original Message-----
> From:	Patrick McManus [SMTP:mcmanus@AppliedTheory.com]
> Sent:	Saturday, August 02, 1997 11:12 AM
> To:	kweide@tezcat.com
> Cc:	http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
> Subject:	Re: Using Content-Encoding and Content-Disposition
> together
> In a previous episode Klaus Weide said...
> ::
> <http://www.w3.org/Protocols/HTTP/1.1/draft-ietf-http-v11-spec-08.txt.
> gz>.
> :: This is currently being served with headers (among others)
> :: 
> ::   Content-Encoding: gzip
> ::   Content-Type: text/plain
> :: 
> :: If one wanted to add a Content-Disposition header, should that be
> :: 
> ::   Content-Disposition: xxx;
> filename="draft-ietf-http-v11-spec-08.txt.gz"
> :: 
> :: or
> :: 
> ::   Content-Disposition: xxx;
> filename="draft-ietf-http-v11-spec-08.txt"
> I'd argue strongly that the second one is the right way, though the
> 19.6.1 definition of Content-Disposition doesn't help much. If it
> isn't the second one, than there is no way (well, cd is just a hint,
> but you get the idea) to save an unencoded version to disk that was
> transferred encoded.. a typical reason for saving the resource to disk
> is for interoperations with other software on the client machine, and
> then if you've got no other local software that knows how to the
> decoding, you're SOL.. that's going to be a problem for platforms like
> windows and mac where the web UA may be the only thing going that
> understands 'deflate' on a typical installation..
> even using the second option as the right way doesn't prevent the UA
> from
> saving a compressed version for an entity that was transferred encoded
> (a checkbox in the save-as dialog indicating that would be a good
> implementation in my mind..)
> :: Current usage (typically larger files, which will be saved in
> :: compressed form) suggests the first alternative.  If
> fwiw - netscape for unix implements it's save-as for the above
> resource as plain text. (the second option, though it isn't driven by
> a content-disposition: header)
> -P
Received on Monday, 4 August 1997 18:08:21 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:03 UTC