W3C home > Mailing lists > Public > public-bpwg-ct@w3.org > October 2008

Re: Web browsers, HTTP and transcoding

From: Tom Hume <Tom.Hume@futureplatforms.com>
Date: Fri, 17 Oct 2008 09:54:04 +0100
Cc: Rotan Hanrahan <rotan.hanrahan@mobileaware.com>, public-bpwg-ct <public-bpwg-ct@w3.org>
Message-Id: <3A33F996-FFA5-4EB6-A741-5F08E5137AC0@futureplatforms.com>
To: Francois Daoust <fd@w3.org>

Has an approach of not transcoding content types explicitly used for  
data rather than data+presentation (e.g. text/xml) been considered?

On 17 Oct 2008, at 08:51, Francois Daoust wrote:

> In the end, Rotan is right, it is just impossible to identify HTTP  
> messages intended for "web browsing" using a deterministic  
> algorithm. Some "magic" is involved, and it simply cannot work in  
> 100% of all cases. Adding a "Cache-Control: no-transform" directive  
> in an XHR call (fairly simple to do, provided you know you have to  
> do it, that is) is the only way to go to make sure CT-proxies would  
> leave the message untouched.

Future Platforms Ltd
e: Tom.Hume@futureplatforms.com
t: +44 (0) 1273 819038
m: +44 (0) 7971 781422
company: www.futureplatforms.com
personal: tomhume.org
Received on Friday, 17 October 2008 08:56:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:06:30 UTC