Very Bizarre

This is very bizarre. Could someone else have a look at this? Maybe you
can see something I'm overlooking. Go here:

http://www.newsletters.forbes.com/en...n/deliver.php4

U: bugtest P: test

Enter 1 for "How many files in this delivery?" and select a file to
upload, in one of the listed formats. Scroll down and click "Test Email".

You should get

Cannot modify header information - headers already sent in
/usr/home/enpusr/enews/auth.php3 on line 49

Cannot modify header information - headers already sent by (output
started at /usr/home/enpusr/enews/auth.php3:49) in
/usr/www/users/enpusr/enews/admin/deliverx.php4 on line 83

There are a number of very weird things about this. First, auth.php3 is
used by every single page in the application, but only has a problem with
this one. Second, the second message is saying output started in
auth.php3 on line 49, but that's a header() call:

header("Set-Cookie: pk=$NewKey; path=/; domain=.$AuthDomain");

The third and most bizarre thing is if you omit the file count, this is
an application error, and deliverx.php4 processes it just fine -- it
makes it through auth.php3 and everything else.

And even more bizarre than that is the fact that this code has been
working fine for a long time, and I haven't changed anything.

Don't let the .php3 extension fool you, it's all PHP4; I just haven't
gotten around to changing some of the file extensions.

Any ideas?

--
Alan Little
Phorm PHP Form Processor
http://www.phorm.com/

"Alan Little" <alan@n-o-s-p-a-m-phorm.com> wrote in message
news:Xns95046F1936B3Falanphormcom@216.196.97.132.. .[color=blue]
> This is very bizarre. Could someone else have a look at this? Maybe you
> can see something I'm overlooking. Go here:
>
> http://www.newsletters.forbes.com/en...n/deliver.php4
>
> U: bugtest P: test
>
> Enter 1 for "How many files in this delivery?" and select a file to
> upload, in one of the listed formats. Scroll down and click "Test Email".
>
> You should get
>
> Cannot modify header information - headers already sent in
> /usr/home/enpusr/enews/auth.php3 on line 49
>
> Cannot modify header information - headers already sent by (output
> started at /usr/home/enpusr/enews/auth.php3:49) in
> /usr/www/users/enpusr/enews/admin/deliverx.php4 on line 83
>
> There are a number of very weird things about this. First, auth.php3 is
> used by every single page in the application, but only has a problem with
> this one. Second, the second message is saying output started in
> auth.php3 on line 49, but that's a header() call:
>
> header("Set-Cookie: pk=$NewKey; path=/; domain=.$AuthDomain");
>[/color]

No, it said "headers already sent" in auth.php3 on line 49... and then you
demonstrated exactly that.

The second message indicates the error occurred on line 83 of deliverx.php4.
What does that line look like?

- Virgil

Carved in mystic runes upon the very living rock, the last words of
Virgil Green of comp.lang.php make plain:
[color=blue]
> "Alan Little" <alan@n-o-s-p-a-m-phorm.com> wrote in message
> news:Xns95046F1936B3Falanphormcom@216.196.97.132.. .[color=green]
>> This is very bizarre. Could someone else have a look at this? Maybe
>> you can see something I'm overlooking. Go here:
>>
>> http://www.newsletters.forbes.com/en...n/deliver.php4
>>
>> U: bugtest P: test
>>
>> Enter 1 for "How many files in this delivery?" and select a file to
>> upload, in one of the listed formats. Scroll down and click "Test
>> Email".
>>
>> You should get
>>
>> Cannot modify header information - headers already sent in
>> /usr/home/enpusr/enews/auth.php3 on line 49
>>
>> Cannot modify header information - headers already sent by (output
>> started at /usr/home/enpusr/enews/auth.php3:49) in
>> /usr/www/users/enpusr/enews/admin/deliverx.php4 on line 83
>>
>> There are a number of very weird things about this. First, auth.php3
>> is used by every single page in the application, but only has a
>> problem with this one. Second, the second message is saying output
>> started in auth.php3 on line 49, but that's a header() call:
>>
>> header("Set-Cookie: pk=$NewKey; path=/; domain=.$AuthDomain");
>>[/color]
>
> No, it said "headers already sent" in auth.php3 on line 49... and then
> you demonstrated exactly that.[/color]

Yes, but the second error says that's where output started.
[color=blue]
> The second message indicates the error occurred on line 83 of
> deliverx.php4. What does that line look like?[/color]

It's a Location: header

header("Location: deliver.php4?err=10");

Something I just noticed is that it's trying to generate an "invalid file
format" error, which should not be happening, as I'm uploading a PDF
file, which is valid. So, more weirdness.

--
Alan Little
Phorm PHP Form Processor
http://www.phorm.com/

Carved in mystic runes upon the very living rock, the last words of Alan
Little of comp.lang.php make plain:
[color=blue]
> This is very bizarre. Could someone else have a look at this? Maybe
> you can see something I'm overlooking. Go here:[/color]

It turned out that something had gone funny with the way the web server
was handling file uploads; apparently it was dumping part of the file
into the response, or something. I don't know. It was the client who put
me onto the solution, actually. He noticed that there was another upload
page that was giving the same error, and said, "Looks like it has
something to do with file uploads." I then noticed that PHP was giving a
UPLOAD_ERR_PARTIAL error. On a hunch I had the ops people restart the
http daemon, and it straightened right out.

Still, a very bizarre error.

--
Alan Little
Phorm PHP Form Processor
http://www.phorm.com/

On Thu, 10 Jun 2004 11:41:33 -0500, Alan Little
<alan@n-o-s-p-a-m-phorm.com> wrote:
[color=blue]
>Carved in mystic runes upon the very living rock, the last words of
>Virgil Green of comp.lang.php make plain:
>[color=green]
>> "Alan Little" <alan@n-o-s-p-a-m-phorm.com> wrote in message
>> news:Xns95046F1936B3Falanphormcom@216.196.97.132.. .[color=darkred]
>>> This is very bizarre. Could someone else have a look at this? Maybe
>>> you can see something I'm overlooking. Go here:
>>>
>>> http://www.newsletters.forbes.com/en...n/deliver.php4
>>>
>>> U: bugtest P: test
>>>
>>> Enter 1 for "How many files in this delivery?" and select a file to
>>> upload, in one of the listed formats. Scroll down and click "Test
>>> Email".
>>>
>>> You should get
>>>
>>> Cannot modify header information - headers already sent in
>>> /usr/home/enpusr/enews/auth.php3 on line 49
>>>
>>> Cannot modify header information - headers already sent by (output
>>> started at /usr/home/enpusr/enews/auth.php3:49) in
>>> /usr/www/users/enpusr/enews/admin/deliverx.php4 on line 83
>>>
>>> There are a number of very weird things about this. First, auth.php3
>>> is used by every single page in the application, but only has a
>>> problem with this one. Second, the second message is saying output
>>> started in auth.php3 on line 49, but that's a header() call:
>>>
>>> header("Set-Cookie: pk=$NewKey; path=/; domain=.$AuthDomain");
>>>[/color]
>>
>> No, it said "headers already sent" in auth.php3 on line 49... and then
>> you demonstrated exactly that.[/color]
>
>Yes, but the second error says that's where output started.[/color]

The "output" in this case is the first error message.

--
David ( @priz.co.uk )