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 jonsiddle
Recipients jonsiddle
Date 2011-06-28.13:37:27
SpamBayes Score 0.0029214004
Marked as misclassified No
Message-id <1309268248.69.0.295956213219.issue12431@psf.upfronthosting.co.za>
In-reply-to
Content
Issue8280 fixed an issue where the fragment was being sent to the server (and returned by get_selector).

Unfortunately the fix means that the "full" URL stored in the Request no longer includes the fragment either.

This is in contradiction to the documentation which states:

 Request.get_full_url()
  Return the URL given in the constructor.

Yet:

 >>> import urllib2
 >>> urllib2.Request("http://host/path#fragment").get_full_url()
 'http://host/path'

The particular use case is a custom scheme handler, which should be able to use the whole of the opaque part of the URL to operate. Ie, our code wants to do something like this:

 urllib2.Request("foo://opaquestring#opaquestring").get_full_url()
History
Date User Action Args
2011-06-28 13:37:28jonsiddlesetrecipients: + jonsiddle
2011-06-28 13:37:28jonsiddlesetmessageid: <1309268248.69.0.295956213219.issue12431@psf.upfronthosting.co.za>
2011-06-28 13:37:28jonsiddlelinkissue12431 messages
2011-06-28 13:37:27jonsiddlecreate