Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#12683 closed (duplicate)

PATH_INFO must not be overridden when it matches the SCRIPT_NAME

Reported by: Gustavo Narea Owned by: nobody
Component: HTTP handling Version: 1.1
Severity: Keywords: wsgi, path_info, script_name
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

In the WSGI handler (django.core.handlers.wsgi), you set the PATH_INFO to "/" if it equals the SCRIPT_NAME, as a workaround for #8490.

There's no sane way to work around this at the WSGI middleware/app level, so I'd suggest not to do nothing in Django and make sure it gets fixed in the affected servers instead.

People deploying Django applications should not investigate whether the path where they want to "mount" the application happens to be used as PATH_INFO too by such an application.

It's Lighttpd's fault after all.

Change History (3)

in reply to:  description comment:1 by Gustavo Narea, 14 years ago

Replying to Gustavo:

so I'd suggest not to do nothing in Django

Just in case, I meant "I'd suggest to do nothing in Django".

comment:2 by Karen Tracey, 14 years ago

Resolution: → duplicate
Status: new → closed

Isn't this #8874?

in reply to:  2 comment:3 by Gustavo Narea, 14 years ago

Replying to kmtracey:

Isn't this #8874?

Yes, it is. Sorry!

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