Bugs item #3235340, was opened at 2011-03-22 12:33
Message generated for change (Comment added) made by andreas_kupries
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=112883&aid=3235340&group_id=12883
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: uri
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Will Duquette (duquette)
Assigned to: Andreas Kupries (andreas_kupries)
Summary: uri::split mishandles fragment
Initial Comment:
The uri::split command mishandles the "fragment" of http:// URIs in two ways:
1. If the URI includes a query, e.g., http://myserver.com/foo?bar=baz#quux, the fragment is treated as part of the query.
2. The "fragment" key is only included in the dictionary returned by uri::split if a fragment is found. All of the other optional URI components are included with an empty value when the component is omitted.
----------------------------------------------------------------------
>Comment By: Andreas Kupries (andreas_kupries)
Date: 2011-03-22 21:41
Message:
Fixed in head, both split and join. Bumped to version 1.2.2.
----------------------------------------------------------------------
Comment By: Will Duquette (duquette)
Date: 2011-03-22 12:42
Message:
Aha!
uri::split and uri::join are presuming that the fragment *precedes* the
query. But it can't, I think, because the fragment is handled by the user
agent, and isn't properly part of the URI at all, whereas the query most
certainly is.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=112883&aid=3235340&group_id=12883
|