Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:127125 X-Original-To: internals@lists.php.net Delivered-To: internals@lists.php.net Received: from php-smtp4.php.net (php-smtp4.php.net [45.112.84.5]) by qa.php.net (Postfix) with ESMTPS id 60CB51A00BC for ; Thu, 17 Apr 2025 07:22:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1744874415; bh=wkYXBXNoc0ZcX7wweokPx0cvv8y4baAvcFq0SFoQ58w=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=mAjzWu1DfC12Uws6pDVXbiM/YW5+mhqQsIZ9E43F+3MdjuonzJqa+FHgClH2X+nMx /2ZdiltjqEpIQDEqnixeECW4+EuLHU22IzFzfsktE4mh0ys07FH64wPR74o5kU70pG SjPVfHyjuzhJIQbQ1GOkjjvi07Qv+KhGdl9muEyhzRw1adbne6UQttqTlsQPpuz7uc g9ubPYfppQdM/1g7LumU4Q8HjKIt+7hckyFKZPj5BKovXxjg8lsJ5NsS0J00rT4QAu n/RCWBorxWll70+phnOctItNVRLogBGQaXZlq2LvGCIQxTR//OIJIN9zl5Nyf8f2ga T8K13vxjIMqdg== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 232A618004F for ; Thu, 17 Apr 2025 07:20:15 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-0.2 required=5.0 tests=BAYES_20,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=4.0.0 X-Spam-Virus: No X-Envelope-From: Received: from chrono.xqk7.com (chrono.xqk7.com [176.9.45.72]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Thu, 17 Apr 2025 07:20:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be; s=mail20171119; t=1744874554; bh=eVD9J4cA62nD6nUTaZsL83YeWL0mmCoLWsvv7IVn2Uc=; h=MIME-Version:Date:From:To:Cc:Subject:In-Reply-To:References: Message-ID:Content-Type:from:to:cc:subject:message-id; b=NMVFEsLUY2gYHpVneRBwwHdaCSonUA4n1Ei6uqFVW56hJh1SkXHJYZ2Ai+NaG83WF ZObBxJe7yx9HZoNNf88BtQ3TSQWtgKQ/7EXMcQwprS22c0HxvEr+GCPg1C6ILqVR7c CoBCv+DG4u7/v2BGsF9TZkY7ee4EOmbf6YOvKLTDBqrG1dNHQy46e2XRrrKGAZ4L1i I8l+92M+cIWDccSGUqnw2ROqVITYT5MrkxoyDnhk3HcLQMiLuhTsjZfhtcOms22uIV tzRn7jEhaflsl68FYhOTLfh/r39LGfee1f8N8IUdeaLTBtCxe4bZc4bGaqwUNtgt30 Ec+KJZ20ZxQrg== Precedence: bulk list-help: list-post: List-Id: internals.lists.php.net x-ms-reactions: disallow MIME-Version: 1.0 Date: Thu, 17 Apr 2025 09:22:34 +0200 To: =?UTF-8?Q?M=C3=A1t=C3=A9_Kocsis?= Cc: Internals Subject: Re: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API In-Reply-To: References: <1BCB4144-231D-45EA-A914-98EE8F0F503A@automattic.com> <8E614C9C-BA85-45D8-9A4E-A30D69981C5D@automattic.com> <8df04e01-deac-404b-beb7-cd982423db63@bastelstu.be> <33427cd03035ef084245c44290b56a55@bastelstu.be> Message-ID: <0aa1eefc3941bdea0092e935074daa58@bastelstu.be> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=) Hi Am 2025-04-15 23:55, schrieb Máté Kocsis: > This was one of my (unspoken) ideas as well. I used to think there must > have been a correct logic > for percent-decoding of WHATWG components, but if none of us can come > up > with a sensible > idea, then it's best not to try it, I agree. Sweet. I believe this was/is the last remaining blocker for the RFC or is there still anyone else from your side that needs to be discussed? I need to give the RFC another read once you made the adjustment to remove the WhatWg raw methods (and adjusted the corresponding explanations), but I think I'm happy then :-) ----- For the latest changes from Tuesday, I see that you added the WhatWg-specific `InvalidUrlException`. The `Uri\InvalidUriException` however still has the `$errors` property. I think you might have forgotten to remove it, since the Rfc3986 implementation / the base exception does not expose any errors, right? Best regards Tim Düsterhus