Page 1 of 1

Installation Problems -> Error 500

Posted: Tue Feb 15, 2005 4:26 am
by Jo Mager
Hi!

I just tried to install s9y on my webserver. I downloaded 0.7.1 from Sourceforge and extracted the contents to www.mydomain.com/serendipity.
But when I goto this URL, I get this famous internal server error...

My error-log says:

Tue Feb 15 00:11:22 2005] [error] [client 133.23.88.22] malformed header from script. Bad header=HTTP/1.0 200\r\n: /home/domains/mydomain.com/cgi-bin/php4

I'm running apache, mysql and php in cgi-mode...

What else do you need to know?

Thank you,
Jo

Re: Installation Problems -> Error 500

Posted: Tue Feb 15, 2005 10:21 am
by garvinhicking
This has been fixed in Serendipity 0.8

Please edit your index.php and search for "HTTP/1.0 200 \r\n" line, and remove the \r there, then everything should run.

Regards,
Garvin

Still Installation Problems -> Error 500

Posted: Tue Feb 15, 2005 11:54 am
by Jo Mager
Hi...

Removed the "\r", but now, my errorlog just tells me:
[Tue Feb 15 11:49:27 2005] [error] [client 133.23.88.22] malformed header from script. Bad header=HTTP/1.0 200\n: /home/domains/mydomain.com/cgi-bin/php4

What to try next? Could there be a problem with mod_rewrite or cgi-mode php?

Jo

Re: Still Installation Problems -> Error 500

Posted: Tue Feb 15, 2005 12:33 pm
by garvinhicking
Hi!

I'm so sorry, I told you the wrong thing! Either you need to remove the \n as well, or you need to write this:

Code: Select all

header("HTTP 1/0 200\r\n");
because currently the header output is in single quote, but double quotes would be needed!

Regards,
Garvin

Posted: Wed Feb 16, 2005 12:35 am
by Guest
I changed it to doublequotes, but still the same problem...

[Wed Feb 16 00:29:00 2005] [error] [client 133.23.88.22] malformed header from script. Bad header=HTTP/1.0 200: /home/domains/mydomain.com/cgi-bin/php4

Posted: Wed Feb 16, 2005 11:31 am
by garvinhicking
I'm sorry, then it seems that your CGI-configuration of PHP doesn't allow to emit headers.

Just delete the header() line then and set URL rewriting to "NONE" in configuration later on - then you should have no problems.

Regards,
Garvin