ID: 5653
Updated by: rick@ozrock.com
Reported By: schulte@delta7.de
Status: No Feedback
Bug Type: Other web server
Operating System: Linux
PHP Version: 4.0.5
New Comment:
I also am using Apache 2 and PHP 4.2.1 WIN32 (with the apache2
API)....
and only the last cookie is set.
Previous Comments:
------------------------------------------------------------------------
[2002-06-10 21:27:23] rick@ozrock.com
I also am using Apache 2 and PHP 4.2.1 WIN32 (with the apache2 API).
------------------------------------------------------------------------
[2002-05-29 14:20:41] bouke_haarsma@hotmail.com
i'm using apache 2.0.36 and php 4.2.1, and since I'm using apache the
cookie problems appeared.
------------------------------------------------------------------------
[2002-02-02 06:40:15] sander@php.net
No feedback was provided for this bug, so it is being suspended.
If you are able to provide the information that was requested,
please do so and change the status of the bug back to "Open".
------------------------------------------------------------------------
[2002-01-11 16:45:03] lobbin@php.net
Can this be reproduced with the PHP 4.1.1, and perhaps the latest
roxen/pike?
------------------------------------------------------------------------
[2001-08-16 12:55:28] cynic@php.net
[2001-08-16 12:24:36] aldem-php@aldem.net
There is small problem in Roxen's SAPI, which arises when duplicate
headers are sent out.
While playing with some PHP apps with Roxen, I found that regardless
how many cookies are
set in PHP code, only one is sent to the browser.
Investigation shows that Roxen's SAPI uses Pike's type "mapping" to
send
headers, which (of course) doesn't allow duplicate headers (in my case
"Set-Cookie") to be sent, i.e. only last one is sent, since subsequesnt
calls to
set header with the same name will replace previous.
Proposed solution: use array instead of mapping. It will require
changes in Roxen module
as well, of course, but this should not be difficult.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/5653--
Edit this bug report at http://bugs.php.net/?id=5653&edit=1