Comments on: When User Agent Sniffing Goes Horribly Wrong

By: Casey

Casey — Sat, 03 Jan 2009 04:12:15 +0000

I have had a few clients who have gotten in trouble with UA sniffing. I always try to avoid sniffing the UA and if I really need to I will only make minor changes to the page.

By: David Doran’s Media Blog » Blog Archive » Hiding and Cloaking

David Doran’s Media Blog » Blog Archive » Hiding and Cloaking — Mon, 13 Oct 2008 18:02:39 +0000

[...] In a follow-up post Richard reveals that for a period of time after the site going online the Google Bot was also blocked from the site. [...]

By: Tim

Tim — Tue, 12 Feb 2008 08:30:01 +0000

Jan, yeah using the default behaviour is a good suggestion.

Meanwhile you can use http://www.browserobject.com/useragent.aspx to detect for the browser type to make sure your CSS works correctly.

By: Jan

Jan — Thu, 06 Sep 2007 09:22:19 +0000

Why should people detect the user agent? For example, you design 3 different versions of your CSS or HTML (because of compatibility): MIE, Fireforx, Opera. OK… and what about other browsers/user agents? It’s senseless.

It’s better to write “Do you see this page incorrectly? Use this browser at no cost!” and place a link to the browser’s download area there. Just my opinion…

BTW, I always check the page under Win OS (MIE,Firefox,Opera) and under Linux before publishing any HTML/CSS update.

By: fmk

fmk — Wed, 14 Feb 2007 23:46:10 +0000

they may have fixed the UA issue, but they’re still screwing up redirecting the old pages. it’s unbelievable that anyone woudl simply flush all what little google-juice the old pages earned.