Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:96341 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 85908 invoked from network); 13 Oct 2016 16:54:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Oct 2016 16:54:30 -0000 Authentication-Results: pb1.pair.com smtp.mail=cmbecker69@gmx.de; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=cmbecker69@gmx.de; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.15.19 as permitted sender) X-PHP-List-Original-Sender: cmbecker69@gmx.de X-Host-Fingerprint: 212.227.15.19 mout.gmx.net Received: from [212.227.15.19] ([212.227.15.19:54887] helo=mout.gmx.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CE/4F-41968-34CBFF75 for ; Thu, 13 Oct 2016 12:54:29 -0400 Received: from [192.168.2.103] ([217.82.231.87]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0M1F72-1b1ekA1jL6-00tAvK; Thu, 13 Oct 2016 18:54:22 +0200 To: David Walker , Nikita Popov References: Cc: PHP internals Message-ID: <6c571887-c24f-0f11-26b0-5f67b5e7a170@gmx.de> Date: Thu, 13 Oct 2016 18:54:58 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:FucrX8ux4nKv1pFvj432xDDK7Pr+YD6OaCNUZqcVKgNpargkXaO L67sJbj8sgv3JzQZaQ5nD+Qam+gfDXxuw/JcDCD67pm9r8A/5MCvYv+DfVGdB1Ce/Hiudkn h9Dgi/o7VDl2SB12KrvAkJ2m+T/ohyulKiT9BD9avY4v5q2/gqPQC+SA/VaVslQpTzpyoGk CqDEKbzILG7rkMvuVQXlQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:vqU7AkzBRNU=:VkdMv6AMvDUYAqr7ruSnmD XL75o9JgyVuGwzllhmk88zyPCDDbd9aKs3Tvar2p9BM7UPAuVYoUZUxAT0ydYQQP2sbrxUJNr P0FoXGWo+ablIyQvj/XaurjJYj5mzbsc2FC0nAWjE2hV2EYvNDmhO0U3fMyl2FrVAKlna4qTl HIJh090AYT1CQLtujjuRhRmHdn2WerZC/hY6HP225KmRqHstBeBdB5oMCOW13GGRAdzmp849D 19pNCXEvlFc3UrMCKNQ5P6qaC0V2FjyEnZrmsiMJYR5/yGR+7XN22gkE/InlaVBLHKEFt/oBl jBXw8MT6r2BreRIId5AvsdSH8ASz1MJF3VH6cVxe+1i9C+GRr1nDPsuHz2/7tpimMoewvVF/Q kqIdsUvx9QS2WihNSe6WMZGAKaa7jOjMifpqCLhwgT3+23q+IcXwDYszDStOS8DYe/g5uzf78 tPrBC8GZPJO6aZWz8EBnOMS8EW9aOYlokptqnSL72C+u3N3rGUJse3td2Z/VBZn6lMhTZj+cU QJF2IESyfE2bnGPDnsIi/z36M7lTKot+xAOHHTLwWERTuIgRDqRIACF2Lwf0JFLjMj+69AHVa ODnZ+8PkrAL0Jr7lSH2S8Fo4XhIPNW2zv/+P2bKWEk5zLkScmZxjBxD5MjDCQ8C/s/12YDog/ ccbfwNo4t326JkCgHRmnlQHLcGg+VDIQ9x9cBNXlO9iQw+0c4Y/s114CqZ25pgRj66hfLFWEd /LKdrjIhRPVhd2s2Pzagi0xHJF8JFtCPIvdjBcx0MWhPYVvodtQ8TsFlVUO5SpOloRu6ZPe0j SYLSeul Subject: Re: [PHP-DEV] [RFC] Bug #72811 - Replacing parse_url() From: cmbecker69@gmx.de ("Christoph M. Becker") On 07.10.2016 at 16:45, David Walker wrote: > On Fri, Oct 7, 2016 at 4:37 AM Nikita Popov wrote: > >> Are you aware of the WHATWG URL standard [1]? Quoting the first goal >> statement: >> >>> Align RFC 3986 and RFC 3987 with contemporary implementations and >> obsolete them in the process. (E.g., spaces, other "illegal" code points, >> query encoding, equality, canonicalization, are all concepts not entirely >> shared, or defined.) URL parsing needs to become as solid as HTML parsing. > > I was not. I assume that WHATWG ought to supersede the IETF standards on > the subject. I can obviously make an implementation follow the standards > and algorithms set out in this doc. That might be hard, because WHATWG has "living standards", i.e. they can change over time. If we state that our new functionality conforms to WHATWG's URL standard we have to always apply the latest changes even into revisions, potentially causing BC breaks. -- Christoph M. Becker