Opened 20 years ago

Closed 20 years ago

Last modified 19 years ago

#1641 closed defect (fixed)

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

Reported by: django@… Owned by: Adrian Holovaty
Component: Core (Other) Version:
Severity: normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

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 (1)

wsgi_handler_fix_r2714.diff​ (678 bytes ) - added by django@… 20 years ago.
patch makes WSGI handler cope with absent QUERY_STRING

Download all attachments as: .zip

Change History (3)

by django@…, 20 years ago

Attachment: wsgi_handler_fix_r2714.diff​ added

patch makes WSGI handler cope with absent QUERY_STRING

comment:1 by django@…, 20 years ago

Summary: WSGIRequest.get_full_path should permit absent QUERY_STRING → [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.

comment:2 by Adrian Holovaty, 20 years ago

Resolution: → fixed
Status: new → closed

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

Note: See TracTickets for help on using tickets.
Back to Top