<?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: Stop http Pipeline from overloading your server, using connlimit iptables</title>
	<atom:link href="http://www.frederico-araujo.com/2009/01/25/stop-http-pipeline-from-overloading-your-server-with-iptables/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.frederico-araujo.com/2009/01/25/stop-http-pipeline-from-overloading-your-server-with-iptables/</link>
	<description>Ruby, Rails, OSX and linux sysadmin</description>
	<lastBuildDate>Thu, 02 Sep 2010 08:03:21 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mark Nottingham</title>
		<link>http://www.frederico-araujo.com/2009/01/25/stop-http-pipeline-from-overloading-your-server-with-iptables/comment-page-1/#comment-40</link>
		<dc:creator>Mark Nottingham</dc:creator>
		<pubDate>Wed, 28 Jan 2009 02:41:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.frederico-araujo.com/?p=79#comment-40</guid>
		<description>Allowing pipelining doesn&#039;t increase connection usage (although it does have other problems); that&#039;s the other connection limit settings.

The approach you take above doesn&#039;t work for proxies that have a large number of users behind them (e.g., ISPs like AOL) or large networks behind NAT (e.g., corporate networks), because traffic from a number of users will appear to come from one IP address (or a small pool of them). This will cause your site to look like it&#039;s down (or more likely, flapping up and down) if more than a handful of people is looking at your site.

Yes, people who abuse servers are annoying. Probably the best solution is to move to a server that doesn&#039;t consume so many resources per-connection. I might also take it up with mozilla to put some constraints on this setting, so as to make it more responsible.

Cheers,</description>
		<content:encoded><![CDATA[<p>Allowing pipelining doesn&#8217;t increase connection usage (although it does have other problems); that&#8217;s the other connection limit settings.</p>
<p>The approach you take above doesn&#8217;t work for proxies that have a large number of users behind them (e.g., ISPs like AOL) or large networks behind NAT (e.g., corporate networks), because traffic from a number of users will appear to come from one IP address (or a small pool of them). This will cause your site to look like it&#8217;s down (or more likely, flapping up and down) if more than a handful of people is looking at your site.</p>
<p>Yes, people who abuse servers are annoying. Probably the best solution is to move to a server that doesn&#8217;t consume so many resources per-connection. I might also take it up with mozilla to put some constraints on this setting, so as to make it more responsible.</p>
<p>Cheers,</p>
]]></content:encoded>
	</item>
</channel>
</rss>
