Re: PHP 4.0 Bug #8744 Updated: call to header() causes CGI error

Here are two typical lines from the log: the first is a successful page load (code 200) and the second is the CGI error after the redirect (502) Note that in the IIS log format it is normal for a space to separate the URL and the Querystring. 2001-01-16 17:20:30 192.168.1.29 - GET /success/ProbRev.php3 EmpID=5&New=Y 200 0 378 Mozilla/4.0+(compatible;+MSIE+5.5;+Windows+98;+Win+9x+4.90) http://192.168.1.30/success/InterimRevSelect.php3?EmpID=5 2001-01-16 17:20:30 192.168.1.29 - GET /success/ProbRev.php3 EmpID=5&ProbRevID=12 502 0 374 Mozilla/4.0+(compatible;+MSIE+5.5;+Windows+98;+Win+9x+4.90) http://192.168.1.30/success/InterimRevSelect.php3?EmpID=5 ----- Original Message ----- From: "Bug Database" <php-dev@lists.php.net> To: <emily@crytech.com> Sent: Tuesday, January 16, 2001 12:12 PM Subject: PHP 4.0 Bug #8744 Updated: call to header() causes CGI error > ID: 8744 > Updated by: derick > Reported By: emily@crytech.com > Old-Status: Open > Status: Feedback > Bug Type: IIS related > Assigned To: > Comments: > > Can you tell us what is in the logs of IIS? > > Previous Comments: > -------------------------------------------------------------------------- - > > [2001-01-16 14:07:45] emily@crytech.com > Our situation is similar to that in bug report 8571, particularly situations 1 and 2. After adding, updating or deleting a record to a MSSQL database, the user is referred to this function (stored in file which is included in each page): > > function pageRedirect($inURL) { > header("Location: $inURL"); > exit; > } > > $inURL is never exactly the same as the current URL - either you are redirected to a completely different file name, or to the same file name with a different query string appended. > > The record modification part always completes successfully in MSSQL, and the header() function sends the user to the new URL, but this error occurs: > > [start] > CGI ERROR > CGI application misbehaved by not returning a complete set of headers. The headers that it > did return are: > [end] > > ... and any code in the page that the user has been redirected to is NOT executed. If the user clicks refresh, it does and all is well. > > This is a PHP web application being ported from a Linux/mySQL environment, where it works, so it appears to be an IIS-specific issue. > > Thanks in advance for any feedback. > > -------------------------------------------------------------------------- - > > > Full Bug description available at: http://bugs.php.net/?id=8744 > >