ID: 36641 Updated by: [EMAIL PROTECTED] Reported By: sreinecke at feverxl dot de -Status: Open +Status: Bogus Bug Type: Documentation problem Operating System: all PHP Version: Irrelevant New Comment:
Read it as "It differs from RFC 1738 in THAT spaces are encoded as +". Otherwise sentense would be "It differs from RFC 1738 WHERE spaces are encoded". Maybe it's a bit ambiguous but clear from context. Previous Comments: ------------------------------------------------------------------------ [2006-03-07 09:55:20] sreinecke at feverxl dot de Yes, thats true. But the manual says wrongly that spaces are encoded as (+) signs in RFC1738. see: http://www.php.net/manual/en/function.urlencode.php ------------------------------------------------------------------------ [2006-03-07 09:35:09] [EMAIL PROTECTED] urlencode() encodes space as +, RFC 1738 as %20. ------------------------------------------------------------------------ [2006-03-07 09:18:52] sreinecke at feverxl dot de Description: ------------ urlencode documentation: Returns a string in which all non-alphanumeric characters except -_. have been replaced with a percent (%) sign followed by two hex digits --> AND SPACES ENCODES AS PLUS (+) SIGNS <--. It is encoded the same way that the posted data from a WWW form is encoded, that is the same way as in application/x-www-form-urlencoded media type. This DIFFERS from the RFC1738 encoding (see rawurlencode()) in that for historical reasons, --> SPACES ARE ENCODED AS PLUS (+) SIGNS. <-- ... Where is the difference? Thank you, Steffen Reproduce code: --------------- http://www.php.net/manual/en/function.urlencode.php Expected result: ---------------- irrelevant Actual result: -------------- see description ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=36641&edit=1
