<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Chrome Frame&#8217;s Shifty User-Agent</title>
	<atom:link href="http://blog.footle.org/2009/12/15/chrome-frames-shifty-user-agent/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.footle.org/2009/12/15/chrome-frames-shifty-user-agent/</link>
	<description>(intr.v.) 1. To waste time; trifle. 2. To talk nonsense. (n.) Nonsense; foolishness</description>
	<lastBuildDate>Mon, 10 May 2010 23:21:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Lawrence</title>
		<link>http://blog.footle.org/2009/12/15/chrome-frames-shifty-user-agent/comment-page-1/#comment-1247</link>
		<dc:creator>Lawrence</dc:creator>
		<pubDate>Wed, 24 Mar 2010 20:47:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.footle.org/?p=120#comment-1247</guid>
		<description>Hi Brad, we&#039;ve run into the same issue. Like you we also invalidate sessions when the user agent changes and this behavior from Chrome Frame seems to be causing problems for our users too. We&#039;ll probably have to do what you did as well -- strip the chromeframe part off the user agent string before comparing it.

We&#039;ve also run into a similar problem with IE8 -- it can change it&#039;s behavior mid-session and switch over into &quot;IE7 compatibility mode&quot;. When it does that, the UA string switches to MSIE/7.x from MSIE/8.x. As we&#039;ll do with the chromeframe issue, our solution was to modify the user agent string before doing the check -- masking out the version number in IE user agent strings to end up with MSIE/#.# no matter whether it is 7 or 8.

Like you I wonder if this security measure is even worth doing still.

---Lawrence</description>
		<content:encoded><![CDATA[<p>Hi Brad, we&#8217;ve run into the same issue. Like you we also invalidate sessions when the user agent changes and this behavior from Chrome Frame seems to be causing problems for our users too. We&#8217;ll probably have to do what you did as well &#8212; strip the chromeframe part off the user agent string before comparing it.</p>
<p>We&#8217;ve also run into a similar problem with IE8 &#8212; it can change it&#8217;s behavior mid-session and switch over into &#8220;IE7 compatibility mode&#8221;. When it does that, the UA string switches to MSIE/7.x from MSIE/8.x. As we&#8217;ll do with the chromeframe issue, our solution was to modify the user agent string before doing the check &#8212; masking out the version number in IE user agent strings to end up with MSIE/#.# no matter whether it is 7 or 8.</p>
<p>Like you I wonder if this security measure is even worth doing still.</p>
<p>&#8212;Lawrence</p>
]]></content:encoded>
	</item>
</channel>
</rss>
