[issue1432] Strange behavior of urlparse.urljoin

Facundo Batista <[EMAIL PROTECTED]> added the comment: Commited in revs 65679 and 65680. Thank you all!! -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___

[issue1432] Strange behavior of urlparse.urljoin

Senthil <[EMAIL PROTECTED]> added the comment: Hi Facundo, I think, we can go ahead and commit the changes. Got a response in Web-SIG that,previous RFC2396 listed behavior is invalid (in a practical sense) and the current patch fixes it. ___ Python tracker <[E

[issue1432] Strange behavior of urlparse.urljoin

Facundo Batista <[EMAIL PROTECTED]> added the comment: Senthil: We should ask for advice in the web-sig list to see if this is enough a "bug to be fixed" now that we're in beta for the releases. Thanks! ___ Python tracker <[EMAIL PROTECTED]>

[issue1432] Strange behavior of urlparse.urljoin

Senthil <[EMAIL PROTECTED]> added the comment: Patch for py3k Added file: http://bugs.python.org/file11054/issue1432-py3k.diff ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue1432] Strange behavior of urlparse.urljoin

Changes by Senthil <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file9035/urlparse.patch ___ Python tracker <[EMAIL PROTECTED]> ___

[issue1432] Strange behavior of urlparse.urljoin

Senthil <[EMAIL PROTECTED]> added the comment: Yes, I agree with you, Roman. I have made changes to urlparse.urljoin which would behave confirming to RFC3986. The join of BASE ("http://a/b/c/d;p?q";) with REL("?y") would result in "http://a/b/c/d;p?y"; as expected. I have added a set of testca

[issue1432] Strange behavior of urlparse.urljoin

Changes by Alexandr Zamaraev <[EMAIL PROTECTED]>: -- nosy: +shura_zam ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list ma

[issue1432] Strange behavior of urlparse.urljoin

Roman Petrichev <[EMAIL PROTECTED]> added the comment: Senthil, please read the RFC3986 text, not only examples. [Page 31] contains exact algorithm how to handle this case. --cut-- if (R.path == "") then T.path = Base.path; if defined(R.query) then T.query = R.query; else T.q

[issue1432] Strange behavior of urlparse.urljoin

Changes by Christian Heimes: -- priority: -> normal versions: -Python 2.4 __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list

[issue1432] Strange behavior of urlparse.urljoin

Senthil added the comment: If we observe carefully in the urlparse.py and test_urlparse.py, over the releases from Python 2.3 to Python 2.6, the changes required for supporting RFC2396 has been implemented. (RFC2396 replaced 1808 in URL Specification.) But the header of urlparse.py still says it

[issue1432] Strange behavior of urlparse.urljoin

Isaac Morland added the comment: RFC 1808 has been obsoleted by RFC 3986: http://tools.ietf.org/html/rfc3986 __ Tracker <[EMAIL PROTECTED]> __ ___ Pytho

[issue1432] Strange behavior of urlparse.urljoin

Isaac Morland added the comment: Issue 1637, Issue 1779700, and Issue 1462525 also relate to this problem. -- nosy: +ijmorlan __ Tracker <[EMAIL PROTECTED]> __

[issue1432] Strange behavior of urlparse.urljoin

Fantix King added the comment: This issue also causes similar behavior on some libraries like mechanize which depend on urljoin -- nosy: +fantix __ Tracker <[EMAIL PROTECTED]> __ _

[issue1432] Strange behavior of urlparse.urljoin

yan added the comment: That sounds great, thanks a lot. __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue1432] Strange behavior of urlparse.urljoin

Senthil added the comment: Yes, you are right. test_urlparse also does not consider the scenarios wherein the relative url +starts with a query like ?y. This needs to be addressed. I shall code the patch to fix it. __ Tracker <[EMAIL PROTECTED]>

[issue1432] Strange behavior of urlparse.urljoin

yan added the comment: Not really, it's just for PATH component. But the QUERY and PARAMETER are not the same. just check the RFC1808. 5.1. Normal Examples Base: http://a/b/c/d;p?q#f> ?y = http://a/b/c/d;p?y> ;x = http://a/b/c/d;x> __ Tracker <[EM

[issue1432] Strange behavior of urlparse.urljoin

Senthil added the comment: Not really. RFC 1808, on which urlparse module is based, defines the following for the PATH component when joining the relative URL to Base URL. Step 6: The last segment of the base URL's path (anything following the rightmost slash "/", or the entire pa

[issue1432] Strange behavior of urlparse.urljoin

New submission from yan: When I use python 2.4/2.5, I found a strange behavior like this: urlparse.urljoin("http://www.python.org/[EMAIL PROTECTED]","[EMAIL PROTECTED]") It will return "http://www.python.org/[EMAIL PROTECTED]". But I think it should be "http://www.python.org/[EMAIL PROTECTED]",