|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #6685 %20 mis-converted in GET mechanism
Submitted: 2000-09-12 13:39 UTC Modified: 2002-12-06 19:29 UTC
Avg. Score:5.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:0 (0.0%)
Same OS:1 (100.0%)
From: Assigned:
Status: Wont fix Package: Scripting Engine problem
PHP Version: 4.0.2 OS: *
Private report: No CVE-ID: None
Have you experienced this issue?
Rate the importance of this bug to you:

 [2000-09-12 13:39 UTC]


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2000-09-12 13:41 UTC]
And what would you expect it to do? You cannot have variable names with spaces. 
 [2000-09-12 13:46 UTC]

 [2000-09-16 17:59 UTC]
On the second though, you _can_ have variables with spaces (actually, you can name variable with every string you can put into variable), so I don't quite understand the maning of that variable name translation. Do we really need it? Anybody will have problems if we remove it?
 [2000-11-21 03:35 UTC]
I think that having spaces in variable names is not
a good thing (tm). could someone please explain me 
how it would be useful at all?

 [2000-11-21 15:37 UTC]

 [2002-06-02 13:29 UTC]
Seems not important enough to anybody... suspending.
 [2003-03-05 05:11 UTC] flystop at gmx dot net
The problem is not only the conversion of spaces but all characters not allowed in variable names. With register_globals=Off the keys in the superglobals should not be changed I think. Sometimes it IS important to use the original names (e.g. in my case passing cookie-data to external pages which use dots in cookie names).

I do think many people who rely on the translation could have problems if it is removed completely.

Maybe a configuration option could be used? This way everybody can decide to use the translation or not.
PHP Copyright © 2001-2018 The PHP Group
All rights reserved.
Last updated: Tue Jul 17 20:01:44 2018 UTC