Bug #55511 [Com]: broken parse_url
| From: | nikolai dot luthman at gmail dot com | Date: | Fri, 26 Aug 2011 00:38:18 +0000 |
| Subject: | Bug #55511 [Com]: broken parse_url | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-162938@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=55511&edit=1
ID: 55511
Comment by: nikolai dot luthman at gmail dot com
Reported by: p4ul dot sincl4ir at gmail dot com
Summary: broken parse_url
Status: Open
Type: Bug
Package: *URL Functions
Operating System: linux
PHP Version: 5.4SVN-2011-08-25 (snap)
Block user comment: N
Private report: N
New Comment:
> From what I can gather from http://www.w3.org/Addressing/URL/url-spec.txt,GƇ
> ÿzq”
áêYOõ : is
not allowed in urls.
The path part obviously...
Previous Comments:
------------------------------------------------------------------------
[2011-08-26 00:34:29] 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-25 23:22:48] 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)
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=55511&edit=1