go to bug id or search bugs for
note: parse_url() will fragment with #[0-9]+; type encodings within the query
that the filter be less greedy, or the function include this behaviour in the documentation
Add a Patch
Add a Pull Request
Could you please provide a test script showing the behaviour you're describing.
Based on what you've written, I do not know what needs to be documented.
expected output (unless documented):
Hash characters are not valid within a URL, except to delimit a fragment. RFC
1738 (http://www.ietf.org/rfc/rfc1738.txt) explicitly indicates under "2.2. URL
Character Encoding Issues" that the hash character *must* be encoded for the URL
to be valid.
The parse_url() reference indicates in several places that malformed URLs will
likely incur issues. As such, I don't feel it's warranted to document each way a
URL can be malformed.
imho, as parse_url actually splits on fragment (which i would assume isnt
actually sent in the HTTP request of a URL), i expected parse_url() to work on
URLs found in the wild (ie. URLs intended for a browsers address bar, xHTML
display) eg. a URL captured from a page anchor href tag.
but again, i wouldnt have realised that a URL encoded with a HTML entity
(regardless of proper context) would be considered malformed.