#24967: FORCE_SCRIPT_NAME causes HttpResponseRedirect to fail
-------------------------------------+-------------------------------------
     Reporter:  seanherron           |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  Core (URLs)          |                  Version:  1.8
     Severity:  Normal               |               Resolution:
     Keywords:  SCRIPT_NAME,         |             Triage Stage:
  FORCE_SCRIPT_NAME,redirect,HttpResponseRedirect|  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by seanherron):

 The problem appears to happen with any combination of FORCE_SCRIPT_NAME
 (`foo`, `/foo`, or `/foo/`).  I've tested with pretty much any combination
 of things I could think of, even trying with the full domain name, but
 haven't been able to get around the issue.

--
Ticket URL: <https://code.djangoproject.com/ticket/24967#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.073f06000eddb97c06c914b1b6c82790%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to