From d58e23d38326694360b0775571ba3513c1630039 Mon Sep 17 00:00:00 2001 From: Joshua Slive Date: Fri, 6 Oct 2000 00:56:48 +0000 Subject: [PATCH] Be a little more explicit about the consequences of ErrorDocument xxx http://.... git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@86411 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/core.html | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/docs/manual/mod/core.html b/docs/manual/mod/core.html index 0da1557172..52504df999 100644 --- a/docs/manual/mod/core.html +++ b/docs/manual/mod/core.html @@ -837,12 +837,18 @@ ErrorDocument 403 "Sorry can't allow you access today"

Note that when you specify an ErrorDocument that points to a remote URL (ie. anything with a method such as "http" in -front of it) Apache will send a redirect to the client to tell it +front of it), Apache will send a redirect to the client to tell it where to find the document, even if the document ends up being on the -same server. This has several implications, the most important being -that if you use an "ErrorDocument 401" directive then it must -refer to a local document. This results from the nature of -the HTTP basic authentication scheme. +same server. This has several implications, the most important being +that the client will not receive the original error status code, but +instead will receive a redirect status code. This in turn can confuse +web robots and other clients which try to determine if a URL is valid +using the status code. In addition, if you use a remote URL in an +ErrorDocument 401, the client will not know to prompt the +user for a password since it will not receive the 401 status +code. Therefore, if you use an "ErrorDocument 401" directive +then it must refer to a local document. +

Prior to version 2.0, messages were indicated by prefixing them with a single unmatched double quote character. -- 2.50.1