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 martin.panter
Recipients albertsmuktupavels, martin.panter
Date 2015-05-13.06:54:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1431500048.13.0.44705978678.issue24032@psf.upfronthosting.co.za>
In-reply-to
Content
This is not how URL joining is meant to work. For example if the base URL “. . ./foo.php?param=10” produces a HTML file with a relative link to “bar.php”, the parent path should be joined on, but not the query part.

I understand the Python implementation is meant to more or less follow the RFC. See the second example at <https://tools.ietf.org/html/rfc3986.html#section-5.4> which is the same form as your case, and shows the query part being removed:

Base URI: http://a/b/c/d;p?q
Relative reference: "g"
Target URL: "http://a/b/c/g"

There are occasionally cases where keeping the base query, or even joining two sets of query parameters together, is desirable. But these cases are rare and urljoin() is not meant to handle them.
History
Date User Action Args
2015-05-13 06:54:08martin.pantersetrecipients: + martin.panter, albertsmuktupavels
2015-05-13 06:54:08martin.pantersetmessageid: <1431500048.13.0.44705978678.issue24032@psf.upfronthosting.co.za>
2015-05-13 06:54:08martin.panterlinkissue24032 messages
2015-05-13 06:54:08martin.pantercreate