#31519 [Opn->Csd]: Setting Status: 559 works using php-cgi but not using Apache 2 module

ID: 31519 Updated by: jorton@php.net Reported By: trevor dot wekel at autodesk dot com -Status: Open +Status: Closed Bug Type: Apache2 related Operating System: Windows XP PHP Version: 5.0.3 New Comment: This bug has been fixed in CVS. Snapshots of the sources are packaged every three hours; this change will be in the next snapshot. You can grab the snapshot at http://snaps.php.net/. Thank you for the report, and for helping us make PHP better. Thanks; the descrepancy may just have been timing on picking up the snapshots, the fix was only committed this morning. Previous Comments: ------------------------------------------------------------------------ [2005-01-17 20:38:57] trevor dot wekel at autodesk dot com I just finished building from the PHP 5.0.4 sources detailed below using VS .Net 2003. I built against Apache 2.0.52 headers and applied the necessary resolve.lib patch mentioned on Zend.com. When built locally, php5apache2.dll works correctly! I configured with the following command line: cscript /nologo configure.js --enable-apache2handler --without-libxml Weird. Are there build differences between the posted win32 executables and my local executables? ------------------------------------------------------------------------ [2005-01-17 17:27:04] trevor dot wekel at autodesk dot com The unusual behaviour is still present in the 5.0.4 development snapshot when run as an Apache module. It returns an HTTP 500 status. Is there anything I can do on my end to determine where the response code is being dropped/remapped? Just out of curiousity, I also tried PHP 5.0.4 dev under IIS 5.1. Both the isapi agent and the cgi return the correct response code. However, the isapi agent does not return the descriptive text correctly. ------------------------------------------------------------------------ [2005-01-17 15:06:32] jorton@php.net Please try using this CVS snapshot: http://snaps.php.net/php5-STABLE-latest.tar.gz For Windows: http://snaps.php.net/win32/php5.0-win32-latest.zip ------------------------------------------------------------------------ [2005-01-12 22:02:27] jed@php.net Sorry, cat hit "Submit" while I wasn't looking. http://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html#sec6.1.1 ...is where that is. ------------------------------------------------------------------------ [2005-01-12 22:00:01] jed@php.net From the HTTP/1.1 spec, §6.1.1: "For example, if an unrecognized status code of 431 is received by the client, it can safely assume that there was something wrong with its request and treat the response as if it had received a 400 status code." 5xx is treated as 500 by applications that don't understand it. Why this behavior pops up in SAPI but not CGI, I'm not sure. Perhaps Apache 2 does not parse CGI return codes, but does for built-in modules? ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/31519 -- Edit this bug report at http://bugs.php.net/?id=31519&edit=1