Carl Michael Skog wrote:
> If I save the response of this command with lynx (lynx -dump
> "http://www.formatemp.com/catalog/paynova-reply.php"; > somefile),
> I will get three newlines.
Aha! I knew it. :) See:
http://marc.theaimsgroup.com/?l=php-general&m=110272197009025&w=2
Lynx adds the newli
I am observing.
What does this "extra" header value come from ?
Regards,
Carl Michael Skog
-Original Message-
From: Richard Lynch ceo-at-l-i-e.com |PHP General user list|
[mailto:...]
Sent: den 10 december 2004 22:40
To: .........
Cc: [EMAIL PROTECTED]
Subj
Richard Lynch wrote:
> Carl Michael Skog wrote:
>> I would have thought that the response from a empty php file would
>> also be empty, but, to my surprise, they consist of 3 newlines !!!
>
> I just tried this with an empty PHP file, and got exactly what I
> expected.
>
> A valid response with no c
Carl Michael Skog wrote:
> Some strange results with spurious newlines inserted in the response when
> requesting a php file has led me to investigating what happens when a
> completely empty php-file is requested.
>
> I would have thought that the response from a empty php file would also be
> emp
It seems very unlikely to me that PHP is actually sending extra data. If
it were a bug, unless it was extremely isolated, quite a lot of people
(including me) would definitely have noticed it.
You didn't give any information, so I'm just guessing, here goes.
It could be...
...the unicode bytes,
5 matches
Mail list logo
