Premarure end of script headers

Hello,

i just notice looking in my server log that i have an error with "Premature end of script headers;vbseo.php"

I never had that before till i upgraded to vb4 recently.

spj

Are the any more details about the error? referring page? user agent? etc

Originally Posted by Brian Cummiskey

Are the any more details about the error? referring page? user agent? etc

this is the actual error in apache log

[Thu Apr 22 17:00:34 2010] [error] [client xxxxxxx] Premature end of script headers: vbseo.php, referer: [RELEASE] Touch Pro 2 Cleanup

just a heads up I'm using apache 2.2.15 php 5.3.2 and mysql 5.1.39

Originally Posted by spj8082

this is the actual error in apache log

just a heads up I'm using apache 2.2.15 php 5.3.2 and mysql 5.1.39

any luck? i googled around and found nothing that will help my issue.

Can you please create a support ticket with login details

Originally Posted by Mert Gökçeimam

Can you please create a support ticket with login details

thank you i will sure do..

Replied to your ticket.

ok i believe it's resolved i have the latest Apache program it had something to do with the server config

Originally Posted by spj8082

ok i believe it's resolved i have the latest Apache program it had something to do with the server config

Has the Same Problem. Should i open a Ticket? Or call you tell me ?

Please open a ticket. The ticket under the OP's name doesn't have a conclusion due to lack of response from the customer.

Apparently I have the same error:

500 - Malformed Header

The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the administrator, of ..... and inform them of the time the error occurred, and anything you might have done that may have caused the error.
Error: HTTPd: malformed header from script /vbseo.php

All (3 sites) are with vb 4
Rest of the forum is working, only when I hit new replies I get this error. All are on same server.
I am opening a ticket too.

Got the feedback from hosting: it was an upgrade to php 5.3.6 that was done and most probably this is the cause.

The best thing you can do is examine your error_log to see the exact error details