#1249 [Com]: url_parse() is a bit too strict

ID: 1249 Comment by: ashley at klikgamers dot co dot uk Reported By: kundrat at general-it dot sk Status: Closed Bug Type: URL related Operating System: linux 2.2.1 glibc 2.0.7 PHP Version: 4.0 New Comment: I do not even understand but it sounds like a bug to me... Previous Comments: ------------------------------------------------------------------------ [2004-08-05 16:41:38] derick at derickrethans dot nl Test! ------------------------------------------------------------------------ [2001-05-14 22:08:52] sniper@php.net Fixed in CVS. Now it behaves more consistently. ie. if ? is present, the query key is set. And if # is present, the fragment key is set. --Jani ------------------------------------------------------------------------ [2001-05-07 12:54:49] derick@php.net marking as fix before 4.0.6 ------------------------------------------------------------------------ [2001-05-07 07:57:14] cardinal@php.net If this isn't a bug, it is at least an inconsistency. parse_url('?') doesn't set a query key parse_url('?#fragment') does Neither URL has what I would consider a query string, but the query key is set in the second case. That behavior should be consistent one way or the other, imho. ------------------------------------------------------------------------ [2001-05-02 21:12:26] sniper@php.net To PHP-developers: Does anyone have any thoughts about this? (IMO, this isn't any bug) --Jani ------------------------------------------------------------------------ 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/1249 -- Edit this bug report at http://bugs.php.net/?id=1249&edit=1