This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author orsenthil
Recipients brett.cannon, mnot, orsenthil, ssteiner
Date 2012-01-29.22:46:57
SpamBayes Score 5.9404083e-05
Marked as misclassified No
Message-id <1327877218.61.0.647816047398.issue7097@psf.upfronthosting.co.za>
In-reply-to
Content
>>> urljoin("http://", "//somedomain.com")
results in "http://somedomain.com"

So, I wonder if this  way to specify the relative url properly and not the base-url. 

The test suite of urlparse tries to follow all the advertised scenarios for RFC3986 and also some more tests (which are usually discovered by de-facto scenarios of how other clients (mainly browsers) deal with it. If there is a browser behavior which we should emulate, without breaking existing code, we should consider this, otherwise we could leave this in invalid state.  Thanks!
History
Date User Action Args
2012-01-29 22:46:58orsenthilsetrecipients: + orsenthil, brett.cannon, ssteiner, mnot
2012-01-29 22:46:58orsenthilsetmessageid: <1327877218.61.0.647816047398.issue7097@psf.upfronthosting.co.za>
2012-01-29 22:46:58orsenthillinkissue7097 messages
2012-01-29 22:46:57orsenthilcreate