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

Port and HTTPS often corrupted #49

Open
gzivdo opened this issue Mar 26, 2017 · 1 comment
Open

Port and HTTPS often corrupted #49

gzivdo opened this issue Mar 26, 2017 · 1 comment

Comments

@gzivdo
Copy link

gzivdo commented Mar 26, 2017

If i accessing page directly on 80 port with plain http it still show SERVER_PORT=443 and REQUEST_SCHEME=https
Used config:
RPAF_Enable On
RPAF_ProxyIPs 127.0.0.1
RPAF_Header X-Forwarded-For
RPAF_SetHostName Off
RPAF_SetHTTPS On
RPAF_SetPort On
To reproduce just access first page via proxy and then access directly a few times (suppose corruption occurs in httpd processes).

RPAF_SetHTTPS and RPAF_SetPort is very usefull feature, because only it allow securely determine https proto. With mod_remoteip this is not possible, because any other can set headers.
Also i tried with remoteip set https=on based on server_addr=127.0.0.1 with setenvif, but in that case in .htaccess in if condition both these vars not visible and not usable.

@AndreiG6
Copy link

This is probably a dupe of #42

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

2 participants