php is written in C. In C the null byte represents the end of a string. I don't think php can work around this.

Hihi,pay attention to:

magic_quotes_gpc=on

http://127.0.0.1/test.php?a'aaaa=test

Actual result:
--------------
Array ( [a\'aaaa] => test )


http://127.0.0.1/test.php?a%00aaaa=test

Actual result:
--------------
Array ( [a] => test )

Replenish other example

magic_quotes_gpc=on

http://127.0.0.1/test/test3.php?a%00aaaa=a%00aaaa

Array ( [a] => a\0aaaa )

magic_quotes_gpc=off

http://127.0.0.1/test/test3.php?a%00aaaa=a%00aaaa

Array ( [a] => aaaaa )

And why would you want to pass null byte in the parameter name? 

I want to know is this is bug?

> And why would you want to pass null byte in the parameter name?
Because it's allowed to use "%00" in a query_string ;-) In $_SERVER['QUERY_STRING'] you have the correct value.

It's also allowed, and works, to use "\0" as array key:
| $a = array("a\0aaaa" => "test");
| echo $a["a\0aaaa"].PHP_EOL;
| echo strlen(key($a));
prints:
| test
| 6

This also works:
| $s = 'a%00aaaa=test';
| $s = rawurldecode($s);
| $t = explode('=', $s);
| $a[$t[0]] = $t[1];
| unset($t);
| var_dump($a);

But this not:
| $s = 'a%00aaaa=test';
| $s = rawurldecode($s);
| parse_str($s, $a);
| var_dump($a);

Maybe the problem is:
With a possible "register_globals = on" or only "parse_str($s);", you have an illegal variable name?

So, that is a bug, but maybe a "won't fix" and should be described in the manual?

Regards,
Carsten

No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Close this bug report dup of http://bugs.php.net/bug.php?id=36183