Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:126977 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 2C5D61A00BC for ; Sun, 30 Mar 2025 11:25:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1743333772; bh=hinGQn2plNHhGjxLP7mB35rSXr2WQxU2V3NxMfv+KiM=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=K5+AOUIfGT2F5O8rATSGiM6LAziEt9VuhTmVPssr6Vad+9RnFS/uFq11Bf/16rPQQ AQDo9an9WMMFM58h2ECEovUjqqvbaMvGR3oghbjxAW0baEYBdu2DhQF5Po3z8f1xMP QKYMilyQKgq1Irixzdvcbwto+pvrDF7yQk4gHrr9sCGYQ5zxeYnnGszw+cA1Zcu3cx CMYA46qlX8xzKv7Hcq2J4z4RHAoRSIQ9B67i/ytWyu8LiWrU4f0VuDaQ+5ZjjO9jaU vFHQzVIfQY/fjsjXhyjURvdSlOq8Ih93Hx4EKC6rsK1IvXz4bPPrjWVX4CNoAIQvkB l8dJ5aZDVWe+Q== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id BC582180041 for ; Sun, 30 Mar 2025 11:22:51 +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 ; Sun, 30 Mar 2025 11:22:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be; s=mail20171119; t=1743333917; bh=FArA1zQ6MIBJYGUyqv+lJJtYm9QpoIwCoYa64lYXEPs=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type:from:to:cc:subject:message-id; b=iQCOwsmQfdniOX9atzPU494hoOYw0xM8VR/3s+UvJmnazGBRDI64228/C6PQG5NxB g9bHSENEMHPJU0VJ8Ou4Z0/ZFEAPM/7pxjJMlCee1nTrbnkZc+2lWDmPBxOma1v+gW RPNpIhVGMEQ166qdt6LqQyhrdY6J8UxyyjeiWdEiUjg3MQIIKlcZOFLz4hAGH6tZtz mXP074DmyZXSMkAOdA3BeD7YAO02k5EShNXGJxgRFUj0iH2bJxy1SnmrR68serFiO0 R7BQoJSL/4t91RCsXslJ6FJ+Pds1GFLSvZKV51NCHS5WWLkP4bb8MwiiFz/IbegQwQ Dmh+63ssnjHnQ== Message-ID: <5f088088-d302-4b2d-85e8-ae2f5b3619b6@bastelstu.be> Date: Sun, 30 Mar 2025 13:25:15 +0200 Precedence: bulk list-help: list-post: List-Id: internals.lists.php.net x-ms-reactions: disallow MIME-Version: 1.0 Subject: Re: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API To: "Paul M. Jones" , Ignace Nyamagana Butera Cc: =?UTF-8?B?TcOhdMOpIEtvY3Npcw==?= , PHP Internals List References: <1BCB4144-231D-45EA-A914-98EE8F0F503A@automattic.com> <8E614C9C-BA85-45D8-9A4E-A30D69981C5D@automattic.com> <9bf11a89-39d9-457b-b0ea-789fd07d7370@gmail.com> <6430b9ed-638d-4247-9fa9-d1a9148c382b@gmail.com> <2e95e8fe-7cf0-493f-bd0a-9fff0956baaa@gmail.com> <778194E9-679B-4178-94F8-052FB2C4DA37@pmjones.io> Content-Language: en-US In-Reply-To: <778194E9-679B-4178-94F8-052FB2C4DA37@pmjones.io> 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 On 3/22/25 15:01, Paul M. Jones wrote: > However, WHATWG-URL consistently calls it `username`, putting the URL portion of the RFC at odds with the WHATWG-URL spec. Calling it `username` would be more in line with the spec. That would likely mean calling it `username` in the URI portion of the RFC as well. This makes sense to me. The WHATWG URL standard uses `username`, RFC 3986 uses `user`, but considers that deprecated in favor of the generic `userinfo`. `user` along might be somewhat ambiguous since it could refer to the entire `userinfo` section or to just the part before the first colon. Best regards Tim Düsterhus