<?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: HTTP Redirect buffer overflow</title>
	<atom:link href="http://blog.pahudson.net/archives/286/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.pahudson.net/archives/286</link>
	<description></description>
	<lastBuildDate>Tue, 24 Jan 2012 09:25:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Erik Brooks</title>
		<link>http://blog.pahudson.net/archives/286/comment-page-1#comment-143</link>
		<dc:creator>Erik Brooks</dc:creator>
		<pubDate>Thu, 25 Feb 2010 01:36:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pahudson.net/?p=286#comment-143</guid>
		<description>If I recall there was a limit in a major browser (IE6 I think, might have been 5.5 or Netscape/FF). That it only handled 2048-character URLs, so a 2048 character buffer made sense back in the R5 days.

But I agree, if the general HTTP handles 4k then the redirects should honor that also.</description>
		<content:encoded><![CDATA[<p>If I recall there was a limit in a major browser (IE6 I think, might have been 5.5 or Netscape/FF). That it only handled 2048-character URLs, so a 2048 character buffer made sense back in the R5 days.</p>
<p>But I agree, if the general HTTP handles 4k then the redirects should honor that also.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

