Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:81222 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 49973 invoked from network); 27 Jan 2015 10:40:51 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Jan 2015 10:40:51 -0000 Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.53 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.192.53 mail-qg0-f53.google.com Received: from [209.85.192.53] ([209.85.192.53:37291] helo=mail-qg0-f53.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 58/66-18778-13B67C45 for ; Tue, 27 Jan 2015 05:40:49 -0500 Received: by mail-qg0-f53.google.com with SMTP id a108so10976621qge.12 for ; Tue, 27 Jan 2015 02:40:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=UUsk/lulVaTTQEscfcSzqP+i1rlyRjkWsuu5RfHSZMI=; b=Dp/hWRoQ2eknFhzuCwgDzBfeRBZ08fLt6ZRM2JmMhH5fdRO0oBXoGA8nXeC9yJyKU9 L5AUNGlTpayG4R/LOz7OC0E3r+ku6+lWIBYy01bTwLE5odi0cq3jxTuBQaN9wUc24vjr 1C8NhLi45yUE7ewf8c1/EbEOY3HoacAb5hQSkBWbzz/iz4rMkBwJe/dWfX0uyDq5gZBc 1lXh97uOPPybCj9BtIbieUgpMlz04izV8s9VSo8WA3GJ+7Pbgc5s0339HGTINKJ8UVU9 ncZxwGZjZGJUjh5OWEE4Ayr7YqpCXWMRbTRJcHGTXgyZuXqy7bqyOXrcdKSRyJGX++7w E6cA== X-Received: by 10.224.111.194 with SMTP id t2mr773531qap.86.1422355246423; Tue, 27 Jan 2015 02:40:46 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.229.93.70 with HTTP; Tue, 27 Jan 2015 02:40:06 -0800 (PST) In-Reply-To: <54C7582B.3080202@lsces.co.uk> References: <54C7582B.3080202@lsces.co.uk> Date: Tue, 27 Jan 2015 19:40:06 +0900 X-Google-Sender-Auth: M2d_rPO7KVRFdBpuoojJOrH7zDU Message-ID: To: Lester Caine Cc: "internals@lists.php.net" Content-Type: multipart/alternative; boundary=047d7b604582352515050d9fe307 Subject: Re: [PHP-DEV] Discussion for RFC: Set appropriate/better defaults. From: yohgaki@ohgaki.net (Yasuo Ohgaki) --047d7b604582352515050d9fe307 Content-Type: text/plain; charset=UTF-8 Hi Lester, On Tue, Jan 27, 2015 at 6:19 PM, Lester Caine wrote: > On 27/01/15 02:06, Yasuo Ohgaki wrote: > > Another example is http_build_query(). It should escape ' ' as '%20' by > > default, not '+'. > > The quick response is probably 'why', but I probably know the answer, > becuase some standard has changed. The problem with this one is that > using a '+' sign when encoding page names is so much easier to read than > $20, and many of the systems I'm still supporting have had as a standard > since PHP4 days. Editing stored data to cope with that change is not as > easy as changing code, so what is easy to say in an RFC can have a lot > more deeper implications! I should have mentioned that urldecode() supports both '+' and '%20'. Therefore, there is no compatibility issue as long as stored data is decoded by urldecode(). http://3v4l.org/KcW4V I suppose RFC 1738 user is using urldecode() as rawurldecodoe() cannot decode '+'. So you and your users wouldn't have BC issues. Please let me know if I'm missing something. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --047d7b604582352515050d9fe307--