Bug #6685 Updated: %20 mis-converted in GET mechanism

ID: 6685 Updated by: derick@php.net Reported By: waldschrott@php.net -Status: Analyzed +Status: Suspended Bug Type: Scripting Engine problem Operating System: * PHP Version: 4.0.2 New Comment: Seems not important enough to anybody... suspending. Previous Comments: ------------------------------------------------------------------------ [2000-11-21 15:37:35] waldschrott@php.net well why do you think are cased variables needed? why do we need to be able to use variables containg ä,ö,ü etc. I'd say escpecially with variable variables this could be useful in some cases ------------------------------------------------------------------------ [2000-11-21 03:35:41] sniper@php.net 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? --Jani ------------------------------------------------------------------------ [2000-09-16 17:59:27] stas@php.net 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-09-12 13:46:32] waldschrott@php.net since we all (almost) agree that register_globals should be deprecated ASAP and array indices with spaces are legal and URIs containg QUERYSTRING with them too, well at least the $HTTP_GET_VARS array should contain the non-converted information, if register_globals=on this mechanism can be applied for global variables We shouldn´t obscure URI data. ------------------------------------------------------------------------ [2000-09-12 13:41:29] stas@php.net And what would you expect it to do? You cannot have variable names with spaces. ------------------------------------------------------------------------ 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/6685 -- Edit this bug report at http://bugs.php.net/?id=6685&edit=1