#23173: SCRIPT_URL on WSGI is misinterpreted when PATH_INFO is empty
-------------------------------------+-------------------------------------
     Reporter:  j-sz@…               |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  Core (URLs)          |                  Version:  master
     Severity:  Normal               |               Resolution:
     Keywords:  wsgi, script name,   |             Triage Stage:  Accepted
  negative index slicing             |      Needs documentation:  0
    Has patch:  0                    |  Patch needs improvement:  0
  Needs tests:  0                    |                    UI/UX:  0
Easy pickings:  0                    |
-------------------------------------+-------------------------------------
Changes (by bmispelon):

 * stage:  Unreviewed => Accepted


Comment:

 OK, marking this as `accepted`.

 FYI, it's easier for me to triage your ticket if you provide a concrete
 example of how to trigger the bug because then I know how to try and
 reproduce it.

 If you just point to a line of code, I have to try and figure out
 where/how that code is used and see if there's a way to trigger the bug in
 a normal use-case. This can be hard and time consuming, especially if I'm
 not familiar with the codebase (which is the case here for example).

 This is why I asked for more details in my first comment.

 Thanks.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/23173#comment:3>
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.890ba608c9dceaa7269f193fa4b50d4b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to