Opened 15 years ago

Closed 14 years ago

#13855 closed New feature (wontfix)

urlresolvers' resolve does not work on URLs with query string

Reported by: Mitar Owned by: nobody
Component: Core (Other) Version: 1.2
Severity: Normal Keywords:
Cc: Triage Stage: Design decision needed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

urlresolvers' resolve does not work on URLs with query string passed as an argument. I think it should silently ignore query string the same as URL dispatching does not take into the account query string. The problem is obviously in that those functions work on request.path but I think they should work also on request.get_full_path.

Change History (3)

comment:1 by Łukasz Rekucki, 15 years ago

Triage Stage: Unreviewed → Design decision needed

comment:2 by Graham King, 15 years ago

Severity: → Normal
Type: → New feature

comment:3 by Chris Beaven, 14 years ago

Easy pickings: unset
Resolution: → wontfix
Status: new → closed
UI/UX: unset

request.path could contain a question mark as part of the path.

For example, http://localhost:8000/test%3f results in request.path containing /test?.

On those grounds, I'm closing this ticket as wontfix due to breaking backwards compatibility in a very rare, but reproducible way.

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