[thelist] Is server-side browser-sniffing a bad idea?

[Ben Gustafson]

> > From: Ben Gustafson <ben_gustafson at lionbridge.com>
> [...]
> > I'm not sure if I follow how web caching would alter the HTTP User
> > Agent string that a browser sends to the Web server. Do all clients
> > connecting via a proxy server identify themselves as the 
> first browser
> > that requested the page they are requesting?
> 
> no, it doesn't alter the string... this scenario:
> 
> 1. NN user goes to foo.com...
> 2. proxy intercepts request, sends request to foo.com...
> 3. foo.com responds with NN-specific code...
> 4. proxy caches page, passes to NN user...
> 5. IE user goes to foo.com...
> 6. proxy intercepts request, hands back cached version...
> 7. IE user gets code error, because it was NN page...
> 
> is that any clearer?

Yup. Thanks, aardvark. BTW, this is a bit of a bummer, since sending a page tailored to
the browser is preferable to sending a page full of JavaScript browser detection "ifs".
Maybe forking over the $$$ for BrowserHawk is a good solution...

--Ben