Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The proxy does not manipulate environ RAW_URI/REQUEST_URI the same way as other environ #27

Open
BrianSipos opened this issue Feb 8, 2021 · 0 comments

Comments

@BrianSipos
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant