#36183 [Opn->Fbk]: urlencode wrongly decodes %00-chars
| From: | sniper@php.net | Date: | Sun, 29 Jan 2006 15:04:42 +0000 |
| Subject: | #36183 [Opn->Fbk]: urlencode wrongly decodes %00-chars | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-92593@lists.php.net to get a copy of this message | ||
ID: 36183
Updated by: sniper@php.net
Reported By: karel at linux dot be
-Status: Open
+Status: Feedback
Bug Type: URL related
Operating System: Linux
PHP Version: 4.4.2
New Comment:
Please try using this CVS snapshot:
http://snaps.php.net/php4-STABLE-latest.tar.gz
For Windows:
http://snaps.php.net/win32/php4-win32-STABLE-latest.zip
Previous Comments:
------------------------------------------------------------------------
[2006-01-28 06:02:15] judas dot iscariote at gmail dot com
not reproducible in latest PHP 5 CVS.
------------------------------------------------------------------------
[2006-01-28 00:16:07] karel at linux dot be
Description:
------------
PHP-version: 4.3.11 (linux), and 4.4.0 (windows)
I don't know if this bug is reproducible on any higher version of PHP
as I don't have them to work on.
If you submit a POST/GET/parse_str() to a webpage, where a variable has
an URLencoded string in it, which contains %00. It will end up being
mangled totally.
Just check the reproduce-code, it'll be more clear then my explanation
here.
Reproduce code:
---------------
$comp_me = gzcompress('Compress me', 9);
parse_str( 'var='. urlencode( $comp_me ) );
var_dump( urlencode($var) );
var_dump( urlencode( $comp_me ) );
Expected result:
----------------
I would expect to see 2 urlencoded strings, EXACTLY the same.
Actual result:
--------------
string(42) "x%DAs%CE%CF-%28J-.V%C8M%05%5C0%19%BD%04%3F"
string(41) "x%DAs%CE%CF-%28J-.V%C8M%05%00%19%BD%04%3F"
---------------------------------------^^^
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=36183&edit=1