Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 1118 invoked from network); 23 May 2007 17:34:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 May 2007 17:34:38 -0000 Received: (qmail 65743 invoked by uid 500); 23 May 2007 17:34:32 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 65734 invoked by uid 500); 23 May 2007 17:34:32 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 65723 invoked by uid 99); 23 May 2007 17:34:32 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 May 2007 10:34:32 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [216.8.91.5] (HELO mail.btsb.com) (216.8.91.5) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 May 2007 10:34:25 -0700 X-IronPort-AV: E=Sophos;i="4.14,570,1170655200"; d="scan'208";a="3136101" Received: from unknown (HELO mail.btsb.com) ([10.1.1.2]) by mail.btsb.com with ESMTP; 23 May 2007 12:43:18 -0500 Received: from GWDOMAIN-MTA by mail.btsb.com with Novell_GroupWise; Wed, 23 May 2007 12:37:28 -0500 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.5.5 Date: Wed, 23 May 2007 12:37:12 -0500 From: "Matt Rigor" To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] changing the error status code for forbidden resources Thank you for sharing your knowledge. >>> joshua@slive.ca 5/23/2007 12:05 PM >>> On 5/23/07, Matt Rigor 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 for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org