- From: Kris Zyp <kris@sitepen.com>
- Date: Tue, 9 Sep 2008 22:10:07 -0600
- To: <timeless@gmail.com>
- Cc: <public-webapps@w3.org>
>> Encoding capability isn't really a state in the HTTP sense, >> since it is presumably an immutable characteristic of the server, > > do you really know this? i could have an applet/script/application > which handles decoding of gz... You are using an applet on the server to decode request entities sent from the browser? Besides being very strange, why does that have any impact the server's ability to honestly advertise it's services? > i think a survey of major sites and most web servers would be > appropriate (there are about 100 web servers [and don't forget to get > most deployed versions not just the latest and buggiest], have fun) Are you saying that you think there is a web server that advertises support for alternate decodings of content encodings in request entities, but then doesn't support it? Can you think of what they might alternately have intended by including the Accept-Encoding header? Kris
Received on Wednesday, 10 September 2008 04:10:53 UTC