PATH_INFO must not be overridden when it matches the SCRIPT_NAME
|Reported by:||Gustavo Narea||Owned by:||nobody|
|Severity:||Keywords:||wsgi, path_info, script_name|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
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.