-
Notifications
You must be signed in to change notification settings - Fork 687
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
Support one of stud's methods of passing the client IP to the backend #94
Comments
backported --http-stud-prefix to 1.4 branch. The system is simple you add the list of ip addresses (currently only ipv4) from which a stud prefix (--write-ip stud's option) is expected. --http-stud-prefix 127.0.0.1 --http-stud-prefix 192.168.173.2 will expect a stud prefix on the connections coming from 127.0.0.1 and 192.168.173.2 |
That was fast! Thanks a lot. I will test it first thing tomorrow. |
It seems to be working. Could you also set "wsgi.url_scheme" accordingly? Otherwise apps will not be able to know whether a request was done with SSL or not. Thanks again! |
I think it would be better to directly set the CGI var HTTPS to on, so all of the plugins will benefit from that. As stud is ssl-only i think we are safe (and eventually the user/developer can always change the scheme in its app) |
ok, backported the HTTPS management even in 1.4 branch. Let me know if all is ok |
It is working perfectly. Thanks Roberto! |
This is done. |
It would be great to support one of stud's methods of passing the client IP to the backend:
The text was updated successfully, but these errors were encountered: