Re: Web browsers, HTTP and transcoding

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
t: +44 (0) 1273 819038
m: +44 (0) 7971 781422

Received on Friday, 17 October 2008 08:56:33 UTC