View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0009916 | mantisbt | installation | public | 2008-11-29 20:09 | 2017-01-31 04:05 |
Reporter | seykron | Assigned To | atrol | ||
Priority | normal | Severity | crash | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Platform | x86_64 | OS | Linux | OS Version | Debian Etch 4 |
Product Version | 1.1.5 | ||||
Summary | 0009916: PHP-CGI with FastCGI crashes when Mantis puts an additional Status Header. | ||||
Description | When using PHP under Apache (this seems to occurs in all version since is not a problem from the server) with mod_fastcgi, server triggers a 500 error page. The next outputs could be found in the error log: [error] [client xxx.xxx.xxx] FastCGI: comm with server "/path/to/cgi/php5" aborted: error parsing headers: duplicate header 'Status' The bug could be temporarily solved by comment the next line in the core.php file: if ( OFF == $g_use_iis ) { It just avoid to append a new Status header to the request, and so FastCGI does not became broken. | ||||
Steps To Reproduce | Uncompress Mantis in the document root directory, and try to open the index (installation process). | ||||
Tags | install | ||||
I've seen this myself I think - do you know if there's a way to detect if we're running under fastcgi? (I assume the issue is fastcgi already sends a status header??) Paul |
|
Well, next to some tests, I found a fix but it not seems to be the best. See below: $serverSoft = $_SERVER["SERVER_SOFTWARE"]; if ( (OFF == $g_use_iis) && ($isFcgi === false) ) { It checks the SERVER_SOFTWARE superglobal and next verify if mod_fastcgi is there, but no ones could to assure that everytime this will be accesible... Anyway, it just work. Regards. |
|
Hi, did you report a bug against fastcgi, too? Regards, |
|
We are resolving this issue as "no change required", because it was reported against an old version of MantisBT which is no longer supported. We recommend that you upgrade to the latest stable version [1]; if after doing so the problem still exists, do not hesitate to reopen the issue. |
|