php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #55511 broken parse_url
Submitted: 2011-08-25 23:22 UTC Modified: 2011-08-28 01:13 UTC
From: p4ul dot sincl4ir at gmail dot com Assigned:
Status: Not a bug Package: *URL Functions
PHP Version: 5.4SVN-2011-08-25 (snap) OS: linux
Private report: No CVE-ID: None
View Developer Edit
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: p4ul dot sincl4ir at gmail dot com
New email:
PHP Version: OS:

 

 [2011-08-25 23:22 UTC] p4ul dot sincl4ir at gmail dot com 
Description:
------------
It seems if you pass a url that has a colon followed by a number into parse_url 
it is unable to parse it. i.e /1:2 returns false
but /1:a2 works so maybe something to do with 
the regex?


Test script:
---------------
$testString = "/1:2";
$x = parse_url($testString);
var_dump( $x );

Expected result:
----------------
array(1) { ["path"]=> string(5) "/1:2" } 

Actual result:
--------------
bool(false)

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2011-08-26 00:34 UTC] nikolai dot luthman at gmail dot com 
From what I can gather from http://www.w3.org/Addressing/URL/url-spec.txt, : is 
not allowed in urls.
 [2011-08-26 00:38 UTC] nikolai dot luthman at gmail dot com 
> From what I can gather from http://www.w3.org/Addressing/URL/url-spec.txt, : is 
not allowed in urls.

The path part obviously...
 [2011-08-28 01:13 UTC] aharvey@php.net
-Status: Open +Status: Bogus
 [2011-08-28 01:13 UTC] aharvey@php.net 
Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to report
a bug at http://bugs.php.net/how-to-report.php

That isn't a valid URL, since there's no scheme, and hence parse_url() is within its rights to return false in that case.
 [2014-02-10 14:31 UTC] alex dot nerten at gmail dot com 
I think this is an error in the function, it has a different behaviour:

Test script:
---------------
var_dump(parse_url('/path?arg=value:1'));

Actual result:
--------------
bool(false)

But

Test script:
---------------
var_dump(parse_url('/path?arg=value:234323'));

Actual result:
--------------
array(2) { ["path"]=> string(5) "/path" ["query"]=> string(16) "arg=value:234323" }
 [2016-09-02 08:43 UTC] bugs dot php dot net at chsc dot dk 
The quoted spec has been superseded by RFC 3986 and that does allow colons in the path.

This issue has been duplicated in bug #71646.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved. 		Last updated: Sat Dec 21 17:01:58 2024 UTC