- From: Martin J. Dürst <duerst@it.aoyama.ac.jp>
- Date: Tue, 07 Apr 2009 10:26:08 +0900
- To: Adam Barth <w3c@adambarth.com>
- CC: Lisa Dusseault <lisa.dusseault@messagingarchitects.com>, HTTP Working Group <ietf-http-wg@w3.org>
On 2009/04/07 4:57, Adam Barth wrote: > There isn't really a way to tweak the content sniffing algorithm to > mitigate these issues. Instead, we win here by having every user > agent that performs sniffing use the same algorithm. That way, > vendors of proxies and firewalls can take sniffing into account (if > they choose) when deciding which responses to block or transform. For proxies and firewalls, the story may not be as simple. How will they be able to distinguish between content sent to browsers (where they can assume that the algorithm in this draft applies) and other content? Regards, Martin. -- #-# Martin J. Dürst, Professor, Aoyama Gakuin University #-# http://www.sw.it.aoyama.ac.jp mailto:duerst@it.aoyama.ac.jp
Received on Tuesday, 7 April 2009 01:27:07 UTC