Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:37603
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain ctindustries.net from 216.117.147.250 cause and error)
Message-ID: <482826D4.3010901@ctindustries.net>
Date: Mon, 12 May 2008 07:15:32 -0400
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: PHP Developers Mailing List <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: url encoding rfc 3986 conformance
From: rrichards@ctindustries.net (Rob Richards)

I'd like to update, or at a minimum, add an option for rawurlencode to 
output rfc3986 conforming data.
It basically boils down to just also not encoding the "~" character.

Most of the new technologies doing encoding require this and its 
becoming a pita to write exception code for that one character.

Personally I think the function should just be updated for 3986 
compliance rather than adding any parameter flags.
simple change in url.c
-                       (str[y] > 'z')) {
+                       (str[y] > 'z' && str[y] != '~')) {

possibly updating urlencode as well to keep them working similarly

Rob