Re^2: [Perlwebmail-devel] Troubleshooting
Richard Roberts
PerlWebmail@cardorealm.com
Wed, 10 Jul 2002 10:51:57 +0100
I've been messing about with the permissions, and it doesn't seem to be
that. I tried changing the permissions on a different cgi script, and the
error that came up was no permission, or something.
So what would cause the error to say "Premature end of script headers"? I
think it's an Apache thing, anyone have any idea what it could be?
On 10/07/2002 10:41, "Jørgen Nørgaard" <jnp@anneli.dk> wrote:
>> Date: Tue, 09 Jul 2002 12:41:37 +0100
>> Subject: Re: [Perlwebmail-devel] Troubleshooting
>> From: Richard Roberts <PerlWebmail@cardorealm.com>
>> To: <perlwebmail-devel@jaos.org>
>> Reply-To: perlwebmail-devel@software.jaos.org
>>
>> Hi
>> I've checked the permissions, and they seem to be fine. Just to make sure,
>> what should they be?
>>
>> Also, an Apache security update was installed not that long ago, could that
>> have broken it? I tried downgrading to the older version of PerlWebmail,
>> but I got the same error, so I have a feeling upgrading PWM isn't what broke
>> it.
>
>
> From apache 1.3.19 -> 1.3.22 (or there abouts) and up it has become
> much stricter with permissions.
>
> The directory and the webmail.pl must only be writable by user
> (chmod go-w on dir & file ).
>
>
> Is this relevant?
>
>
>> Any ideas?
>> Thanks
>>
>> On 07/07/2002 09:02, "Jørgen Nørgaard" <jnp@anneli.dk> wrote:
>>
>>>>
>>>>
>>>> Message: 4
>>>> Date: Fri, 05 Jul 2002 18:49:17 +0100
>>>> Subject: Re: [Perlwebmail-devel] Troubleshooting
>>>> From: Richard Roberts <PerlWebmail@cardorealm.com>
>>>> To: <perlwebmail-devel@jaos.org>
>>>> Reply-To: perlwebmail-devel@software.jaos.org
>>>>
>>>> Thanks for the help, here are the results.
>>>>
>>>> I've noticed the problem with the images path, and I've fixed that.
>>>>
>>>> ./webmail.pl
>>>>
>>>> [cardorealm:/Library/WebServer/CGI-Executables] cardo% ./webmail.pl
>>>> (offline mode: enter name=value pairs on standard input)
>>>
>>> Give a ^D (or what ever your EOF is) that should produce valid output.
>>>
>>> If not, check permissions on script and directory it lives in. Newer
>>> apaches are fairly strict with these.
>>>
>>> Cheers,
>
>