Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:51218 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 68375 invoked from network); 5 Jan 2011 12:17:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Jan 2011 12:17:43 -0000 Authentication-Results: pb1.pair.com header.from=tjerk.meesters@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=tjerk.meesters@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.177 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: tjerk.meesters@gmail.com X-Host-Fingerprint: 209.85.216.177 mail-qy0-f177.google.com Received: from [209.85.216.177] ([209.85.216.177:41198] helo=mail-qy0-f177.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9A/44-32752-661642D4 for ; Wed, 05 Jan 2011 07:17:43 -0500 Received: by qyk27 with SMTP id 27so15493563qyk.8 for ; Wed, 05 Jan 2011 04:17:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:received :in-reply-to:references:date:message-id:subject:from:to:cc :content-type; bh=E0kAIXQSKLPd8CNrFS3o5u/5cUYGQvrtVSH8U+xuD4c=; b=D/JkRrphB0Z5xI4vfEZzq4GT5oWNcj3uHliS7VCVXesULm+1cYbqI4bR2bsKnlNWxv eai75zggJllVsleUzNEguKR+DfCsFKK4uUAVe9bEzDJIEtRCUNYRjc1PSIS9lavUc1Gk gV3j6hPaQrQNcMBBKFaBdLbXwm8vXnoEXmCqY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=fWb4V83onkvNADQPmNZhc/+zLBpEBUzq4T+n84GcX/nGx50Xvww4Dr8HwrXaPD8Qln /UkbtsLpBPQ9fFfim5hFcp9Mp5GzzLiHJvmYWxN4zvuT0zdl7XnIrA0yblK8odk+ei6c BOsQ2vi86pJltUn0BxswIexHZ1MAg6jh1XLiY= MIME-Version: 1.0 Received: by 10.224.61.5 with SMTP id r5mr21708474qah.121.1294229859154; Wed, 05 Jan 2011 04:17:39 -0800 (PST) Received: by 10.224.2.82 with HTTP; Wed, 5 Jan 2011 04:17:39 -0800 (PST) Received: by 10.224.2.82 with HTTP; Wed, 5 Jan 2011 04:17:39 -0800 (PST) In-Reply-To: <4D245F5B.3050707@yahoo.co.jp> References: <4D245F5B.3050707@yahoo.co.jp> Date: Wed, 5 Jan 2011 20:17:39 +0800 Message-ID: To: Rui Hirokawa Cc: internals@lists.php.net Content-Type: multipart/alternative; boundary=0015175cb8e40341580499185fca Subject: Re: [PHP-DEV] [PATCH] adding RFC3984 support to http_build_query From: tjerk.meesters@gmail.com (Tjerk Meesters) --0015175cb8e40341580499185fca Content-Type: text/plain; charset=ISO-8859-1 Instead of a boolean, could you add a rfc-xx selection parameter instead, like, in case one would like rfc 3986 instead? On Jan 5, 2011 8:10 PM, "Rui Hirokawa" wrote: > Hello, > > I made a patch to add the RFC-3984 based url-encoding support > into http_build_query(). > > The http_build_query() is quite useful, but, > it isn't based on the official url-encoding scheme (RFC-3984) > for ~ (tilde) and ' '(space). > > I added an optional (the 4th) parameter 'is_rfc3984'. > If it is true (false by default, now), RFC3984 based > url-encoding scheme (it is same as rawurlencode() ) is used. > > A simple example shown as bellow, > > $v = array('foo'=>'m o','boo'=>'[^~]'); > > // result: foo=m+p&boo=%5B%5E%7E5D > echo http_build_query($v, null, '&'); > > // result: foo=m%20p&boo=%5B%5E~5D (RFC-3986 compatible) > echo http_build_query($v, null, '&', true); > > // result: foo=m%20p&boo=%5B%5E~5D (RFC-3986 compatible) > echo rawurlencode($v['foo']).'&'.rawurlencode($v['boo']); > > > I'm going to commit the patch if it is accepted. > > Rui --0015175cb8e40341580499185fca--