Re: Re: Status: 204 and PHP's Content-type
| From: | Timo Haimi | Date: | Fri, 30 Jun 2000 21:32:57 +0000 |
| Subject: | Re: Re: Status: 204 and PHP's Content-type | ||
| References: | 1 2 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-4167@lists.php.net to get a copy of this message | ||
At 03:58 PM 6/30/00 -0500, you wrote:
In article <4.3.2.20000622090531.00bb9580@uto.pop.sci.fi>, uto@stc.cx (Timo H) wrote:From command line it outputs correctly, only the statusline and 2 linefeeds. When I telnet and get it, the server returns 500 Internal Server error. Apache log says: Premature end of script headers: /www/test.cgi. As I said earlier, the format works.. With a normal #!/bin/sh script it works correctly if I output "Status: 204" and 2 linefeeds.. It's a shame I can't do what I want to do with /bin/sh ;) Any help/ideas are appreciated.. -Timo#!/usr/bin/php -q <? echo "Status: 204\n\n"; ?>Hello, Hmm strangely enough, if I run that, it gives me 500 Internal server error. I didn't succeed even in most basic script, echoing the Content-type What if you run it from the command line? What does a raw telnet session reveal?