-
Notifications
You must be signed in to change notification settings - Fork 10
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
php not setting HTTPS #1
Comments
It is sorry for wrong behavior. Would you please check reproducibility with similar modules and tell me the result? https://github.com/ttkzw/mod_rpaf-0.6 |
Unfortunately those do not try to handle X-Forwarded-Proto like you do. I think I will try this in httpd.conf SetEnvIf X-Forwarded-Proto https HTTPS=on and see if php-fpm will obey it, but maybe not by the way, thank you for your work on modifying mod_rpaf, I appreciate it |
Thank you for your quick reply. I am looking forward to hearing from you. |
I've had the same problem. Switching to the current release of https://github.com/gnif/mod_rpaf solved it. From their issue tracker it looks like an issue with mod_rewrite - gnif/mod_rpaf#6 |
Hi @or1can I'm sorry I have misread. |
Any insight why HTTPS is not working? HOST host and remote ip are properly working.
nginx.conf:
proxy_set_header X-Forwarded-Proto $scheme;
apache httpd.conf:
RPAFsethttps On
phpinfo:
_SERVER["HTTP_X_FORWARDED_PROTO"] https
_ENV["HTTP_X_FORWARDED_PROTO"] https
but this does NOT appear
_SERVER["HTTPS"]
Note that everything else works fine via the proxy, hostname, remoteip etc.
The remote_addr is being set to the _SERVER["HTTP_X_REAL_IP"]
What's strange is the port is also being changed
_SERVER["SERVER_PORT"] 443
but I have
RPAFsetport Off
so that should not even be set
in fact I am not even forwarding the port info via prox_set_header
so something else is changing it to 443 and there is nothing in the _server or _env variables that show 443
Is this possible a php-fpm issue where it will not properly set HTTPS ?
The text was updated successfully, but these errors were encountered: