Django

Code

Ticket #1641 (closed: fixed)

Opened 3 years ago

Last modified 2 years ago

[magic-removal][patch] WSGIRequest.get_full_path should permit absent QUERY_STRING

Reported by: django@kieranholland.com Assigned to: adrian
Milestone: Component: Core framework
Version: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: 1 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

Description

As commented in WSGIRequest._get_get the WSGI spec says 'QUERY_STRING' may be absent from the environment. WSGIRequest.get_full_path should allow for this also.

Attachments

wsgi_handler_fix_r2714.diff (0.7 kB) - added by django@kieranholland.com on 04/19/06 18:38:02.
patch makes WSGI handler cope with absent QUERY_STRING

Change History

04/19/06 18:38:02 changed by django@kieranholland.com

  • attachment wsgi_handler_fix_r2714.diff added.

patch makes WSGI handler cope with absent QUERY_STRING

04/19/06 18:44:13 changed by django@kieranholland.com

  • summary changed from WSGIRequest.get_full_path should permit absent QUERY_STRING to [magic-removal][patch] WSGIRequest.get_full_path should permit absent QUERY_STRING.

Patch attached - I needed this fix to use Titus Brown's wsgi_intercept module to interact with Django without a web server.

04/20/06 14:47:22 changed by adrian

  • status changed from new to closed.
  • resolution set to fixed.

(In [2715]) magic-removal: Fixed #1641 -- Changed WSGIRequest.get_full_path() to permit absent QUERY_STRING. Thanks, Kieran Holland

Add/Change #1641 ([magic-removal][patch] WSGIRequest.get_full_path should permit absent QUERY_STRING)




Change Properties
Action