<?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"
	>
<channel>
	<title>Comments on: Secure UTF-8 Input in Rails</title>
	<atom:link href="http://www.igvita.com/2007/04/11/secure-utf-8-input-in-rails/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.igvita.com/2007/04/11/secure-utf-8-input-in-rails/</link>
	<description>A goal is a dream with a deadline.</description>
	<pubDate>Fri, 04 Jul 2008 03:03:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Ilya Grigorik</title>
		<link>http://www.igvita.com/2007/04/11/secure-utf-8-input-in-rails/#comment-66868</link>
		<dc:creator>Ilya Grigorik</dc:creator>
		<pubDate>Thu, 06 Sep 2007 13:39:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.igvita.com/blog/2007/04/11/secure-utf-8-input-in-rails/#comment-66868</guid>
		<description>Antti, thanks for the correction. You're right, I swept some details under the rug when I talked about ISO8859-1. :)</description>
		<content:encoded><![CDATA[<p>Antti, thanks for the correction. You&#8217;re right, I swept some details under the rug when I talked about ISO8859-1. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: antti</title>
		<link>http://www.igvita.com/2007/04/11/secure-utf-8-input-in-rails/#comment-66365</link>
		<dc:creator>antti</dc:creator>
		<pubDate>Tue, 04 Sep 2007 18:32:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.igvita.com/blog/2007/04/11/secure-utf-8-input-in-rails/#comment-66365</guid>
		<description>Um, everything is *not* valid by default in ISO8859-1. The range 0x80-0x9f is invalid. The reasons for this concern legacy terminals and programs: they could drop the 8th bit and interpret those as control characters.

Perhaps you were thinking of code page 1252, aka windows-1252, the bane of many Unix users out there.</description>
		<content:encoded><![CDATA[<p>Um, everything is *not* valid by default in ISO8859-1. The range 0&#215;80-0&#215;9f is invalid. The reasons for this concern legacy terminals and programs: they could drop the 8th bit and interpret those as control characters.</p>
<p>Perhaps you were thinking of code page 1252, aka windows-1252, the bane of many Unix users out there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2007-05-25, or so says Harry Love</title>
		<link>http://www.igvita.com/2007/04/11/secure-utf-8-input-in-rails/#comment-39772</link>
		<dc:creator>links for 2007-05-25, or so says Harry Love</dc:creator>
		<pubDate>Fri, 25 May 2007 16:21:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.igvita.com/blog/2007/04/11/secure-utf-8-input-in-rails/#comment-39772</guid>
		<description>[...] Secure UTF-8 Input in Rails - igvita.com (tags: rubyonrails security unicode utf8) [...]</description>
		<content:encoded><![CDATA[<p>[...] Secure UTF-8 Input in Rails - igvita.com (tags: rubyonrails security unicode utf8) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ilya Grigorik</title>
		<link>http://www.igvita.com/2007/04/11/secure-utf-8-input-in-rails/#comment-36117</link>
		<dc:creator>Ilya Grigorik</dc:creator>
		<pubDate>Sat, 05 May 2007 13:44:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.igvita.com/blog/2007/04/11/secure-utf-8-input-in-rails/#comment-36117</guid>
		<description>Yep, that's the plan, Ruby should be unicode safe as of next big release. In fact, oniguruma is taken directly out of 1.9/2.0. My only worry is, nobody seems to know when to expect 1.9/2.0.</description>
		<content:encoded><![CDATA[<p>Yep, that&#8217;s the plan, Ruby should be unicode safe as of next big release. In fact, oniguruma is taken directly out of 1.9/2.0. My only worry is, nobody seems to know when to expect 1.9/2.0.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ilya Radchenko</title>
		<link>http://www.igvita.com/2007/04/11/secure-utf-8-input-in-rails/#comment-36053</link>
		<dc:creator>Ilya Radchenko</dc:creator>
		<pubDate>Sat, 05 May 2007 05:43:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.igvita.com/blog/2007/04/11/secure-utf-8-input-in-rails/#comment-36053</guid>
		<description>So is there any word on ruby 1.9/2.0 being Unicode-safe? Or would you say this "flaw" should still be addressed?</description>
		<content:encoded><![CDATA[<p>So is there any word on ruby 1.9/2.0 being Unicode-safe? Or would you say this &#8220;flaw&#8221; should still be addressed?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ilya Grigorik</title>
		<link>http://www.igvita.com/2007/04/11/secure-utf-8-input-in-rails/#comment-32359</link>
		<dc:creator>Ilya Grigorik</dc:creator>
		<pubDate>Sat, 14 Apr 2007 04:11:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.igvita.com/blog/2007/04/11/secure-utf-8-input-in-rails/#comment-32359</guid>
		<description>jCris, glad to be of help! 

Chuck, that's a great add-on for Apache. Especially relevant for anyone using page caching. One suggestion though, I would recommend sticking that code into your main config (httpd.conf). Otherwise Apache is forced to read .htaccess on every access, which makes a dent on overall performance.</description>
		<content:encoded><![CDATA[<p>jCris, glad to be of help! </p>
<p>Chuck, that&#8217;s a great add-on for Apache. Especially relevant for anyone using page caching. One suggestion though, I would recommend sticking that code into your main config (httpd.conf). Otherwise Apache is forced to read .htaccess on every access, which makes a dent on overall performance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chuck Bergeron</title>
		<link>http://www.igvita.com/2007/04/11/secure-utf-8-input-in-rails/#comment-32308</link>
		<dc:creator>Chuck Bergeron</dc:creator>
		<pubDate>Fri, 13 Apr 2007 18:27:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.igvita.com/blog/2007/04/11/secure-utf-8-input-in-rails/#comment-32308</guid>
		<description>Wow, great post on very relevant and usable stuff. Thanks!

One thing I also had to do when serving up UTF8 content on my shared hosting provider:

&#62; .htaccess
AddDefaultCharset OFF
AddType text/html;charset=UTF-8 html
AddType text/plain;charset=UTF-8 txt

Cheers!</description>
		<content:encoded><![CDATA[<p>Wow, great post on very relevant and usable stuff. Thanks!</p>
<p>One thing I also had to do when serving up UTF8 content on my shared hosting provider:</p>
<p>&gt; .htaccess<br />
AddDefaultCharset OFF<br />
AddType text/html;charset=UTF-8 html<br />
AddType text/plain;charset=UTF-8 txt</p>
<p>Cheers!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jChris</title>
		<link>http://www.igvita.com/2007/04/11/secure-utf-8-input-in-rails/#comment-32289</link>
		<dc:creator>jChris</dc:creator>
		<pubDate>Fri, 13 Apr 2007 16:36:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.igvita.com/blog/2007/04/11/secure-utf-8-input-in-rails/#comment-32289</guid>
		<description>Thanks for the clear and encouraging take on the black art of character encoding! I've got tthis url in my bug tracker for future reference.</description>
		<content:encoded><![CDATA[<p>Thanks for the clear and encouraging take on the black art of character encoding! I&#8217;ve got tthis url in my bug tracker for future reference.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
