You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of 0.4.6, if the request environ contains a RAW_URI or REQUEST_URI value it is used directly, ignoring the "strip_script_name" constructor parameter.
This makes the proxy have different behavior for WSGI servers which set RAW_URI or REQUEST_URI from those which do not. It seems like a simple fix would be to detect-and-remove the environ['SCRIPT_NAME'] which is a PEP-333 required variable. The other '_URI' environ names are not PEP-333 standard.
As a workaround, a WSGI middleware can strip REQUEST_URI values.
The text was updated successfully, but these errors were encountered:
As of 0.4.6, if the request
environ
contains aRAW_URI
orREQUEST_URI
value it is used directly, ignoring the "strip_script_name" constructor parameter.This makes the proxy have different behavior for WSGI servers which set
RAW_URI
orREQUEST_URI
from those which do not. It seems like a simple fix would be to detect-and-remove theenviron['SCRIPT_NAME']
which is a PEP-333 required variable. The other '_URI' environ names are not PEP-333 standard.As a workaround, a WSGI middleware can strip
REQUEST_URI
values.The text was updated successfully, but these errors were encountered: