|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2016-12-31 00:28 UTC] cmb@php.net
-Package: Feature/Change Request
+Package: URL related
[2020-11-05 13:07 UTC] cmb@php.net
-Status: Open
+Status: Suspended
[2020-11-05 13:07 UTC] cmb@php.net
|
|||||||||||||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Mon Oct 27 14:00:01 2025 UTC |
Description: ------------ I looked myself and determined that the RFC3986 is very spongelike. Compared with other programming languages I noticed that everyone differently converts the RFC. In Python there is a nice feature, that you can tell wich chars have to be safe urllib.quote(s, safe='~'). All chars except this one in the safe parameter are escaped. With PHP you could do this only with a search & replace function which isn't very nice. So i want to suggest, to add likewise one more parameter to the urlencode function. Expected result: ---------------- echo urlencode("Test str \"'.-/", array('\'', '"')); output: Test+str+"'%2E%2D%2F ====== echo rawurlencode("Test str \"'.-/", array('\'', '"')); output: Test%20str%20"'%2E%2D%2F Actual result: -------------- echo urlencode("Test str \"'.-/"); output: Test+str+%22%27.-%2F ====== echo rawurlencode("Test str \"'.-/"); output: Test%20str%20%22%27.-%2F