<div class="toplang">
<p><span>Available Languages: </span><a href="./en/custom-error.html" title="English"> en </a> |
<a href="./es/custom-error.html" hreflang="es" rel="alternate" title="Español"> es </a> |
+<a href="./fr/custom-error.html" hreflang="fr" rel="alternate" title="Français"> fr </a> |
<a href="./ja/custom-error.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
<a href="./ko/custom-error.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> |
<a href="./tr/custom-error.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p>
</div>
- <p>Additional functionality allows webmasters to configure the response
+ <p>Additional functionality allows webmasters to configure the response
of Apache to some error or problem.</p>
- <p>Customizable responses can be defined to be activated in the event of
+ <p>Customizable responses can be defined to be activated in the event of
a server detected error or problem.</p>
- <p>If a script crashes and produces a "500 Server Error" response,
- then this response can be replaced with either some friendlier text or by
+ <p>If a script crashes and produces a "500 Server Error" response,
+ then this response can be replaced with either some friendlier text or by
a redirection to another URL (local or external).</p>
</div>
<div id="quickview"><ul id="toc"><li><img alt="" src="./images/down.gif" /> <a href="#behavior">Behavior</a></li>
<h3>Old Behavior</h3>
- <p>NCSA httpd 1.3 would return some boring old error/problem message
- which would often be meaningless to the user, and would provide no
+ <p>NCSA httpd 1.3 would return some boring old error/problem message
+ which would often be meaningless to the user, and would provide no
means of logging the symptoms which caused it.</p>
<p>The server can be asked to:</p>
<ol>
- <li>Display some other text, instead of the NCSA hard coded
+ <li>Display some other text, instead of the NCSA hard coded
messages, or</li>
<li>redirect to a local URL, or</li>
<li>redirect to an external URL.</li>
</ol>
- <p>Redirecting to another URL can be useful, but only if some
- information can be passed which can then be used to explain and/or log
+ <p>Redirecting to another URL can be useful, but only if some
+ information can be passed which can then be used to explain and/or log
the error/problem more clearly.</p>
- <p>To achieve this, Apache will define new CGI-like environment
+ <p>To achieve this, Apache will define new CGI-like environment
variables:</p>
<div class="example"><p><code>
- REDIRECT_HTTP_ACCEPT=*/*, image/gif, image/x-xbitmap,
+ REDIRECT_HTTP_ACCEPT=*/*, image/gif, image/x-xbitmap,
image/jpeg<br />
- REDIRECT_HTTP_USER_AGENT=Mozilla/1.1b2 (X11; I; HP-UX A.09.05
+ REDIRECT_HTTP_USER_AGENT=Mozilla/1.1b2 (X11; I; HP-UX A.09.05
9000/712)<br />
REDIRECT_PATH=.:/bin:/usr/local/bin:/etc<br />
REDIRECT_QUERY_STRING=<br />
new URL (assuming it's a cgi-script or a cgi-include). The
other variables will exist only if they existed prior to
the error/problem. <strong>None</strong> of these will be
- set if your <code class="directive"><a href="./mod/core.html#errordocument">ErrorDocument</a></code> is an
- <em>external</em> redirect (anything starting with a
- scheme name like <code>http:</code>, even if it refers to the same host
+ set if your <code class="directive"><a href="./mod/core.html#errordocument">ErrorDocument</a></code> is an
+ <em>external</em> redirect (anything starting with a
+ scheme name like <code>http:</code>, even if it refers to the same host
as the server).</p>
</div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
<h2><a name="configuration" id="configuration">Configuration</a></h2>
- <p>Use of <code class="directive"><a href="./mod/core.html#errordocument">ErrorDocument</a></code> is enabled
- for .htaccess files when the
- <code class="directive"><a href="./mod/core.html#allowoverride">AllowOverride</a></code> is set accordingly.</p>
+ <p>Use of <code class="directive"><a href="./mod/core.html#errordocument">ErrorDocument</a></code> is enabled
+ for .htaccess files when the
+ <code class="directive"><a href="./mod/core.html#allowoverride">AllowOverride</a></code> is set to FileInfo.</p>
<p>Here are some examples...</p>
<div class="bottomlang">
<p><span>Available Languages: </span><a href="./en/custom-error.html" title="English"> en </a> |
<a href="./es/custom-error.html" hreflang="es" rel="alternate" title="Español"> es </a> |
+<a href="./fr/custom-error.html" hreflang="fr" rel="alternate" title="Français"> fr </a> |
<a href="./ja/custom-error.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
<a href="./ko/custom-error.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> |
<a href="./tr/custom-error.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p>
<title>Custom Error Responses</title>
<summary>
- <p>Additional functionality allows webmasters to configure the response
+ <p>Additional functionality allows webmasters to configure the response
of Apache to some error or problem.</p>
- <p>Customizable responses can be defined to be activated in the event of
+ <p>Customizable responses can be defined to be activated in the event of
a server detected error or problem.</p>
- <p>If a script crashes and produces a "500 Server Error" response,
- then this response can be replaced with either some friendlier text or by
+ <p>If a script crashes and produces a "500 Server Error" response,
+ then this response can be replaced with either some friendlier text or by
a redirection to another URL (local or external).</p>
</summary>
<section>
<title>Old Behavior</title>
- <p>NCSA httpd 1.3 would return some boring old error/problem message
- which would often be meaningless to the user, and would provide no
+ <p>NCSA httpd 1.3 would return some boring old error/problem message
+ which would often be meaningless to the user, and would provide no
means of logging the symptoms which caused it.</p>
</section>
<p>The server can be asked to:</p>
<ol>
- <li>Display some other text, instead of the NCSA hard coded
+ <li>Display some other text, instead of the NCSA hard coded
messages, or</li>
<li>redirect to a local URL, or</li>
<li>redirect to an external URL.</li>
</ol>
- <p>Redirecting to another URL can be useful, but only if some
- information can be passed which can then be used to explain and/or log
+ <p>Redirecting to another URL can be useful, but only if some
+ information can be passed which can then be used to explain and/or log
the error/problem more clearly.</p>
- <p>To achieve this, Apache will define new CGI-like environment
+ <p>To achieve this, Apache will define new CGI-like environment
variables:</p>
<example>
- REDIRECT_HTTP_ACCEPT=*/*, image/gif, image/x-xbitmap,
+ REDIRECT_HTTP_ACCEPT=*/*, image/gif, image/x-xbitmap,
image/jpeg<br />
- REDIRECT_HTTP_USER_AGENT=Mozilla/1.1b2 (X11; I; HP-UX A.09.05
+ REDIRECT_HTTP_USER_AGENT=Mozilla/1.1b2 (X11; I; HP-UX A.09.05
9000/712)<br />
REDIRECT_PATH=.:/bin:/usr/local/bin:/etc<br />
REDIRECT_QUERY_STRING=<br />
new URL (assuming it's a cgi-script or a cgi-include). The
other variables will exist only if they existed prior to
the error/problem. <strong>None</strong> of these will be
- set if your <directive module="core">ErrorDocument</directive> is an
- <em>external</em> redirect (anything starting with a
- scheme name like <code>http:</code>, even if it refers to the same host
+ set if your <directive module="core">ErrorDocument</directive> is an
+ <em>external</em> redirect (anything starting with a
+ scheme name like <code>http:</code>, even if it refers to the same host
as the server).</p>
</section>
</section>
<section id="configuration">
<title>Configuration</title>
- <p>Use of <directive module="core">ErrorDocument</directive> is enabled
- for .htaccess files when the
- <directive module="core">AllowOverride</directive> is set accordingly.</p>
+ <p>Use of <directive module="core">ErrorDocument</directive> is enabled
+ for .htaccess files when the
+ <directive module="core">AllowOverride</directive> is set to FileInfo.</p>
<p>Here are some examples...</p>
projects / apache / commitdiff