php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #19793 Apache blames the failure of /error.php?error=# with ErrorDocument on PHP
Submitted: 2002-10-06 21:21 UTC Modified: 2002-10-27 19:11 UTC
Votes:1
Avg. Score:5.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:0 (0.0%)
Same OS:1 (100.0%)
From: mordeth at pankurokku dot com Assigned:
Status: No Feedback Package: Apache2 related
PHP Version: 4.2.3 OS: RedHat 7.1
Private report: No CVE-ID: None
View Developer Edit
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: mordeth at pankurokku dot com
New email:
PHP Version: OS:

 

 [2002-10-06 21:21 UTC] mordeth at pankurokku dot com 
I have always used this in my .htaccess:

#  Error document handling:

ErrorDocument   401     /error.php?error=401
ErrorDocument   403     /error.php?error=403
ErrorDocument   404     /error.php?error=404

this works perfectly with PHP on Apache 1.3.x.

Recently, I decided to upgrade PHP and Apache to the newest version of each on a server that I maintain, and first noticed that in directories where I use another .htaccess for password protection, Apache was giving me the 401 page without asking for a username and password, then saying that it was getting a 403 error in trying to load the ErrorDocument.

This made no sense to me, because:

DocumentRoot = /web/mori

drwxrwx--x   24 mordeth  mordeth      4096 Oct  6 21:25 .
-rw-rw-r--    1 mordeth  mordeth      6731 Dec  5  2001 error.php

and in /web:

drwxr-x--x   41 root     web          4096 Oct  1 23:04 .

as you can see...I have the correct perms for Apache to be able to read that document, so I shouldn't be getting 403 errors on it.

After submitting bug #13121 to Apache (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13121), they reject fixing the problem, instead blaming the problem on PHP:

"This is almost certainly a PHP problem, since the default install includes some SSI-generated error documents that work just fine.  Most likely, the reponse status code is getting lost someplace in the PHP filter.  Please ask on the PHP users mailing list, and if they don't have a solution, report it in the PHP bug database."

I fail to see why it'd be PHP's fault that Apache wouldn't do the Auth before serving the ErrorDocument, but hopefully someone can diagnose this.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2002-10-10 10:33 UTC] alindeman@php.net 
Please try using this CVS snapshot:

  http://snaps.php.net/php4-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php4-win32-latest.zip
 [2002-10-27 19:11 UTC] sniper@php.net 
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Fri Dec 27 01:01:28 2024 UTC