On 5/4/07, Fred Tyler <fredty8@xxxxxxxxx> wrote:
Well, it turns out that getting rid of Vary within mod_negotiation isn't as straightforward as I'd hoped, so I've gone and change http_protocol.c in version 1.3.37 and http_filters.c in 2.2.4 so that setting "force-no-vary" does not fall back to HTTP/1.0. The only way I plan to use "force-no-vary" is by putting the following line in httpd.conf: BrowserMatch MSIE force-no-vary With that in mind, can someone who know more about these things than I do comment on the safety of this approach? As long as I limit "force-no-vary" to MSIE, is there any risk of *not* degrading to HTTP/1.0?
It depends what you are varying on and why. You could easily cause proxy caches to send innapropriate variants to clients. Joshua. --------------------------------------------------------------------- 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
|