On Fri, 20 Mar 2009 11:17:13 -0400 Brian Mearns <mearns.b@xxxxxxxxx> wrote: > > I'm not sure content-transfer-encoding is the right header, I think > just Content-encoding is what you want. Otherwise, that should work I > think, but it requires that people's browsers support zip encoding, > which mine, for instance (FF3 on Linux) does not. zip is not a recognised encoding. You'd have to configure a browser to unzip it. gzip is a standard that pretty-much everyone supports. The other standard in the HTTP spec is compress (the older .Z compression). > If you're going to do this and you don't want to lock anybody out > because of browser in-compatibilities, I think you're going to have to > parse the request headers, find out if they support the specified > encoding, and if not, have your server decompress on the fly before > sending. mod_negotiation does that for you. The docs explain it. -- Nick Kew Application Development with Apache - the Apache Modules Book http://www.apachetutor.org/ --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|