#33138 [Bgs]: parse_url() wrongly handles relative URIs with ':'

ID: 33138 User updated by: moriyoshi@php.net Reported By: moriyoshi@php.net Status: Bogus Bug Type: URL related Operating System: Irrelevant PHP Version: 4.3.11 New Comment: Okay, I'm gonna check it out. Thank you for taking care of this. Previous Comments: ------------------------------------------------------------------------ [2005-05-26 05:57:45] iliaa@php.net I've added scheme validation to the code, which coincidentally made your examples work as expected :-) ------------------------------------------------------------------------ [2005-05-25 23:38:00] iliaa@php.net At the moment the code follows the RFC 1738 with some additions, which is the URL specification. As far as adding partial URL support, please consider the following; c?d:e, c?d:, etc... are all valid file names, at least on *NIX. The only bug I see here is that we "break" the spec and allow scheme to contain non-valid chars such as / and ?. In all of the provided examples the path should contain the entire string. ------------------------------------------------------------------------ [2005-05-25 21:02:48] moriyoshi@php.net Wouldn't it be handy if the *URI* syntax (or RFC1808 at least) is supported in addition to the URL syntax? As it can already handle relative pathes just partly at the moment, there shouldn't be no BC problem. ------------------------------------------------------------------------ [2005-05-25 20:49:52] iliaa@php.net There is no requirment to support relative URL. All of the URLs with which URL RFC deals have a sheme or equivalent. ------------------------------------------------------------------------ [2005-05-25 19:03:41] moriyoshi@php.net Is there any specification that suggests relative URI's point to local resources by default? Otherwise parse_url() is not supposed to conform to the RFC. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/33138 -- Edit this bug report at http://bugs.php.net/?id=33138&edit=1