Thank you for sharing your knowledge.

>>> [EMAIL PROTECTED] 5/23/2007 12:05 PM >>>
On 5/23/07, Matt Rigor <[EMAIL PROTECTED]> wrote:
> Joshua,
>
> Three questions in hopes of bettering my understanding of Apache.
>
> Why not just edit the conf file to take the 403 error and have it
> redirect to the Apache 404 error page
> within the error directory? Example below.
>
> ErrorDocument 403 /error/HTTP_NOT_FOUND.html.var
> ErrorDocument 404 /error/HTTP_NOT_FOUND.html.var

Because in addition to the error document itself, the server transmits
a status code as part of the HTTP response. So someone looking at the
full network stream could still see the difference.

>
> As an alternative, why not just edit the actual 403 error page
contents
> to reflect the error you desire.

Same problem.

>
> Finally, You mention that "it's more than a waste of time, it is
> deliberately crippling of HTTP".  Why?

Owen gave a good answer to this. Ask yourself why the authors of the
HTTP spec decided to have status codes in the first place. Or why not
just two codes: success and failure.

Joshua.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server
Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [EMAIL PROTECTED] 
   "   from the digest: [EMAIL PROTECTED] 
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: [EMAIL PROTECTED]
   "   from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to