ID:               18993
 Updated by:       [EMAIL PROTECTED]
 Reported By:      [EMAIL PROTECTED]
-Status:           Analyzed
+Status:           Bogus
 Bug Type:         Documentation problem
 Operating System: Linux
 PHP Version:      4.2.2
 Assigned To:      spic
 New Comment:

arg_separator.input and arg_separator.output have nothing
to do with urlencode() & friends. Please read the comments
in php.ini-dist about what they are meant for..




Previous Comments:
------------------------------------------------------------------------

[2002-08-26 12:09:02] [EMAIL PROTECTED]

After re-investigating the doc, I could not reproduce the error using a
test-script that encoded and decoded a string "?test=one&test=two" with
$cstr=htmlentities(urlencode($str)); with and without changing
arg_separator.


------------------------------------------------------------------------

[2002-08-26 09:50:57] [EMAIL PROTECTED]

I will fix it as soon as possible. 

------------------------------------------------------------------------

[2002-08-26 09:07:30] [EMAIL PROTECTED]

I've found it at http://www.zend.com/manual/function.urlencode.php
Description at:
http://www.php.net/manual/en/function.urlencode.php
is wrong as well:
"You don't need to change PHP's arg_separator for this"
arg_separator _has_ to be set to achive this behaviour.
When I upgraded to 4.2.2 my scripts stop working. Instead of "aa" I got
strings like "amp;aa". After setting the arg_separator which doesn't
need to be changed (according to description) everything is ok.

------------------------------------------------------------------------

[2002-08-26 08:25:26] [EMAIL PROTECTED]

Perhaps changing this sentence to "A more portable way around this is
to use & instead of & as the separator (which is the default
setting in php.ini)" will solve the problem. 

------------------------------------------------------------------------

[2002-08-26 08:12:50] [EMAIL PROTECTED]

Where in the Documentation does this error occur???
I found the expression at the urlencode-Doc. Is this correct??? Could
you describe the bug a bit more detailed???

------------------------------------------------------------------------

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/18993

-- 
Edit this bug report at http://bugs.php.net/?id=18993&edit=1


-- 
PHP Documentation Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to