|
|
Registered User Currently Offline
|
Posts: 4
Join Date: Nov 2005
|
|
Quote: It has sth to do with your php settings.
This is running on a production machine with hundreds of other users -- this exact script runs on it without problem in 99% of times. This is not something to do with the PHP binary, nor is it something we have seen consistently with other php file.
Quote: Run this search on google and read on: [premature end of script headers php 4.3.2] and similar queries. Lots of stuff pops out. One post said that a simple script calling phpinfo produced the error.
The issues which are listed (including but not limited to the one you list above) is referring to when there is a configuration error with either apache or the php handler. A problem of this nature would cause ALL php scripts to return this error message. As clearly outlined previously, this is not the case.
Quote: Another one said anything recursive causes it on his configuration (seo-board uses a recurvise func to addslash $_GET etc. arrays).
Does seo board use this every time index.php is loaded? If not, what specific cases would cause it to use this function?
Quote: Some said the problem is in some parameters in php.ini where too little memory is given to php etc.
Currently there is 8MB being allocated to php, I would be rather concerned if there is a need to increase this for the index page to work in all conditions. To be honest, looking at the code, I would find it very hard to accept this is the problem. As an aside, this type of error will generally crash gracefully with a memory allocation error, provided apache/php are configured correctly, which they are.
Quote: I just don't have time to dig it deeply. Maybe try to upgrade the php to 4.3.10.
As I am sure you can appreciate, upgrading php on a live production server generally isn't something which is very pratical.. And I was hoping that if there is some type of condition within the script which was causing this problem then we could work to having it fixed. Unfortunately, given this is the only code which is exhibiting this sporatic behaviour then I will admit I am a little reluctant to accept that it is an issue within PHP. On this basis, regrettably, the only other recommendation I can provide is to use alternative forum software which is more mature and thus more reliable.
|