#18776 [Opn->Bgs]: using & instead of "&" causes malformed HTTP_REFERER
| From: | markonen@php.net | Date: | Wed, 07 Aug 2002 10:18:50 +0000 |
| Subject: | #18776 [Opn->Bgs]: using & instead of "&" causes malformed HTTP_REFERER | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-16137@lists.php.net to get a copy of this message | ||
ID: 18776
Updated by: markonen@php.net
Reported By: rob@pipgroup.com
-Status: Open
+Status: Bogus
Bug Type: Variables related
Operating System: Win2K
PHP Version: 4.2.2
New Comment:
Actually I think that W3C recommends either & or just a semicolon
as the parameter separator.
You are encountering a user agent issue. PHP doesn't parse the Referer
header; it's there exactly like the user agent sent it.
User agents generally know that a "&" in a href attribute be
decoded and a plain "&" sent to the server when accessing the location.
It seems that your browser doesn't do this for &.
Previous Comments:
------------------------------------------------------------------------
[2002-08-07 06:11:56] rob@pipgroup.com
when using "&" instead of "&" to separate variables passed through
a url causes HTTP_REFERER to include all the url after the first
&.
According to the W3C & should be used to avoid confusion with &
being used as a character entity identifier.
This is a big problem when passing variables out of a page for
processing on a second page which then uses a header() redirect back to
the original page.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=18776&edit=1