<?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 Status Codes and .htaccess ErrorDocuments</title>
	<atom:link href="http://www.askapache.com/htaccess/apache-status-code-headers-errordocument.html/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.askapache.com/htaccess/apache-status-code-headers-errordocument.html</link>
	<description>Advanced Web Development</description>
	<lastBuildDate>Wed, 18 Nov 2009 23:28:48 -0500</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ultimate Htaccess Tutorial for .htaccess files</title>
		<link>http://www.askapache.com/htaccess/apache-status-code-headers-errordocument.html#comment-104761</link>
		<dc:creator>Ultimate Htaccess Tutorial for .htaccess files</dc:creator>
		<pubDate>Tue, 29 Sep 2009 12:55:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com.com/htaccess/wow-i-served-a-page-for-every-single-http-status-code-and-saved-headers-and-content.html#comment-104761</guid>
		<description>[...] Requires a valid user/pass to access the login page[401] [...]</description>
		<content:encoded><![CDATA[<p>[...] Requires a valid user/pass to access the login page[401] [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Some buddy...</title>
		<link>http://www.askapache.com/htaccess/apache-status-code-headers-errordocument.html#comment-94653</link>
		<dc:creator>Some buddy...</dc:creator>
		<pubDate>Wed, 12 Aug 2009 21:54:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com.com/htaccess/wow-i-served-a-page-for-every-single-http-status-code-and-saved-headers-and-content.html#comment-94653</guid>
		<description>The biggest problem with all of the error codes is that they all reply to the request.  This is the reason denial of service attacks work so well.  Every wasteful request gets the attention of the server and it sends off a reply.  

I would love to know why there is no error request that would be sent to &lt;code&gt;/dev/null&lt;/code&gt; - ie don&#039;t reply to the ignored request - just send it to the bitbucket and move on to the next request.  What the world needs is an error code that totally ignores specified errors, IPs, etc.</description>
		<content:encoded><![CDATA[<p>The biggest problem with all of the error codes is that they all reply to the request.  This is the reason denial of service attacks work so well.  Every wasteful request gets the attention of the server and it sends off a reply.  </p>
<p>I would love to know why there is no error request that would be sent to <code>/dev/null</code> &#8211; ie don&#8217;t reply to the ignored request &#8211; just send it to the bitbucket and move on to the next request.  What the world needs is an error code that totally ignores specified errors, IPs, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dharmmotyar</title>
		<link>http://www.askapache.com/htaccess/apache-status-code-headers-errordocument.html#comment-72763</link>
		<dc:creator>Dharmmotyar</dc:creator>
		<pubDate>Mon, 04 May 2009 06:58:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com.com/htaccess/wow-i-served-a-page-for-every-single-http-status-code-and-saved-headers-and-content.html#comment-72763</guid>
		<description>What if the http_status_code ==0 ?? please reply me soon</description>
		<content:encoded><![CDATA[<p>What if the http_status_code ==0 ?? please reply me soon</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Spencer</title>
		<link>http://www.askapache.com/htaccess/apache-status-code-headers-errordocument.html#comment-55992</link>
		<dc:creator>Joe Spencer</dc:creator>
		<pubDate>Tue, 13 Jan 2009 10:22:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com.com/htaccess/wow-i-served-a-page-for-every-single-http-status-code-and-saved-headers-and-content.html#comment-55992</guid>
		<description>Very useful list, thanks.</description>
		<content:encoded><![CDATA[<p>Very useful list, thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vi</title>
		<link>http://www.askapache.com/htaccess/apache-status-code-headers-errordocument.html#comment-54397</link>
		<dc:creator>vi</dc:creator>
		<pubDate>Thu, 08 Jan 2009 07:54:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com.com/htaccess/wow-i-served-a-page-for-every-single-http-status-code-and-saved-headers-and-content.html#comment-54397</guid>
		<description>good article,nifty code, and nice way to simulate the error codes. thanks for all that.
418 is too good to forget</description>
		<content:encoded><![CDATA[<p>good article,nifty code, and nice way to simulate the error codes. thanks for all that.<br />
418 is too good to forget</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AskApache</title>
		<link>http://www.askapache.com/htaccess/apache-status-code-headers-errordocument.html#comment-47726</link>
		<dc:creator>AskApache</dc:creator>
		<pubDate>Tue, 09 Dec 2008 01:01:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com.com/htaccess/wow-i-served-a-page-for-every-single-http-status-code-and-saved-headers-and-content.html#comment-47726</guid>
		<description>&lt;p&gt;&lt;strong&gt;@ Gerald&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;LOL! Thanks buddy, at first I thought you kidding, as I noted your website to be the venerable wireshark.org, which is probably the greatest computer program ever invented.&lt;/p&gt;

&lt;p&gt;I checked it out and sure enough, you were right!  I updated this article and my servers errordocuments to reflect this new info.  Thanks!&lt;/p&gt;


&lt;blockquote cite=&quot;http://tools.ietf.org/html/rfc2324&quot;&gt;
&lt;pre&gt;
Any attempt to brew coffee with a teapot should result in 
the error code &quot;418 I&#039;m a teapot&quot;. The resulting entity body 
MAY be short and stout.
&#160;
7. Security Considerations
&#160;
Anyone who gets in between me and my morning coffee should be
insecure.
&#160;
Unmoderated access to unprotected coffee pots from Internet users
might lead to several kinds of &quot;denial of coffee service&quot; attacks.
The improper use of filtration devices might admit trojan grounds.
Filtration is not a good virus protection method.
&lt;/pre&gt;
&lt;/blockquote&gt;


&lt;p&gt;Classic!&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p><strong>@ Gerald</strong></p>
<p>LOL! Thanks buddy, at first I thought you kidding, as I noted your website to be the venerable wireshark.org, which is probably the greatest computer program ever invented.</p>
<p>I checked it out and sure enough, you were right!  I updated this article and my servers errordocuments to reflect this new info.  Thanks!</p>
<blockquote cite="http://tools.ietf.org/html/rfc2324">
<pre>Any attempt to brew coffee with a teapot should result in
the error code "418 I&#039;m a teapot". The resulting entity body
MAY be short and stout.
&nbsp;
7. Security Considerations
&nbsp;
Anyone who gets in between me and my morning coffee should be
insecure.
&nbsp;
Unmoderated access to unprotected coffee pots from Internet users
might lead to several kinds of "denial of coffee service" attacks.
The improper use of filtration devices might admit trojan grounds.
Filtration is not a good virus protection method.</pre>
</blockquote>
<p>Classic!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gerald Combs</title>
		<link>http://www.askapache.com/htaccess/apache-status-code-headers-errordocument.html#comment-47707</link>
		<dc:creator>Gerald Combs</dc:creator>
		<pubDate>Mon, 08 Dec 2008 17:42:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com.com/htaccess/wow-i-served-a-page-for-every-single-http-status-code-and-saved-headers-and-content.html#comment-47707</guid>
		<description>Return code 418 is defined in &lt;a href=&quot;http://tools.ietf.org/html/rfc2324&quot; rel=&quot;nofollow&quot;&gt;RFC 2324&lt;/a&gt;:


2.3.2 418 I&#039;m a teapot

   Any attempt to brew coffee with a teapot should result in the error
   code &quot;418 I&#039;m a teapot&quot;. The resulting entity body MAY be short and
   stout.
</description>
		<content:encoded><![CDATA[<p>Return code 418 is defined in <a href="http://tools.ietf.org/html/rfc2324" rel="nofollow">RFC 2324</a>:</p>
<p>2.3.2 418 I&#8217;m a teapot</p>
<p>   Any attempt to brew coffee with a teapot should result in the error<br />
   code &#8220;418 I&#8217;m a teapot&#8221;. The resulting entity body MAY be short and<br />
   stout.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Berkeley</title>
		<link>http://www.askapache.com/htaccess/apache-status-code-headers-errordocument.html#comment-47452</link>
		<dc:creator>Berkeley</dc:creator>
		<pubDate>Sun, 23 Nov 2008 02:33:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com.com/htaccess/wow-i-served-a-page-for-every-single-http-status-code-and-saved-headers-and-content.html#comment-47452</guid>
		<description>Learn about .htaccess from the place that gave us BSD and one of the greatest schools in the world: &lt;a href=&quot;http://docs.ocf.berkeley.edu/wiki/How_to_use_.htaccess_file&quot; rel=&quot;nofollow&quot;&gt;Berkeley.edu - how to use .htaccess file&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Learn about .htaccess from the place that gave us BSD and one of the greatest schools in the world: <a href="http://docs.ocf.berkeley.edu/wiki/How_to_use_.htaccess_file" rel="nofollow">Berkeley.edu &#8211; how to use .htaccess file</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AskApache</title>
		<link>http://www.askapache.com/htaccess/apache-status-code-headers-errordocument.html#comment-44071</link>
		<dc:creator>AskApache</dc:creator>
		<pubDate>Mon, 11 Aug 2008 21:46:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com.com/htaccess/wow-i-served-a-page-for-every-single-http-status-code-and-saved-headers-and-content.html#comment-44071</guid>
		<description>&lt;p&gt;&lt;strong&gt;@ abhi&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Those are commonly used to maintain that information internally by the servers.&lt;/p&gt;

&lt;p&gt;I wrote all about it when explaining you can use the &lt;a href=&quot;http://www.askapache.com/htaccess/php-cgi-redirect_status.html&quot; rel=&quot;nofollow&quot;&gt;REDIRECT_URL or REDIRECT_STATUS variables to secure direct access to your binary files&lt;/a&gt;..&lt;/p&gt;


&lt;blockquote cite=&quot;http://www.askapache.com/htaccess/php-cgi-redirect_status.html&quot;&gt;Each new variable will have the prefix REDIRECT_. REDIRECT_ environment variables are created from the CGI environment variables which existed prior to the redirect, they are renamed with a REDIRECT_ prefix, i.e., HTTP_USER_AGENT becomes REDIRECT_HTTP_USER_AGENT. In addition to these new variables, Apache will define REDIRECT_URL and REDIRECT_STATUS to help the script trace its origin. Both the original URL and the URL being redirected to can be logged in the access log.&lt;/blockquote&gt;</description>
		<content:encoded><![CDATA[<p><strong>@ abhi</strong></p>
<p>Those are commonly used to maintain that information internally by the servers.</p>
<p>I wrote all about it when explaining you can use the <a href="http://www.askapache.com/htaccess/php-cgi-redirect_status.html" rel="nofollow">REDIRECT_URL or REDIRECT_STATUS variables to secure direct access to your binary files</a>..</p>
<blockquote cite="http://www.askapache.com/htaccess/php-cgi-redirect_status.html"><p>Each new variable will have the prefix REDIRECT_. REDIRECT_ environment variables are created from the CGI environment variables which existed prior to the redirect, they are renamed with a REDIRECT_ prefix, i.e., HTTP_USER_AGENT becomes REDIRECT_HTTP_USER_AGENT. In addition to these new variables, Apache will define REDIRECT_URL and REDIRECT_STATUS to help the script trace its origin. Both the original URL and the URL being redirected to can be logged in the access log.</p></blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>By: abhi kakade</title>
		<link>http://www.askapache.com/htaccess/apache-status-code-headers-errordocument.html#comment-35578</link>
		<dc:creator>abhi kakade</dc:creator>
		<pubDate>Fri, 01 Feb 2008 10:21:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.askapache.com.com/htaccess/wow-i-served-a-page-for-every-single-http-status-code-and-saved-headers-and-content.html#comment-35578</guid>
		<description>This help is very useful.

I have one problem i am not able to get the value of $_SERVER[&#039;REDIRECT_URL&#039;] i have that script on subdomain can you tell me what is lines required in .htaccess file to get values of $_SERVER[&#039;REDIRECT_URL&#039;]?</description>
		<content:encoded><![CDATA[<p>This help is very useful.</p>
<p>I have one problem i am not able to get the value of $_SERVER['REDIRECT_URL'] i have that script on subdomain can you tell me what is lines required in .htaccess file to get values of $_SERVER['REDIRECT_URL']?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
