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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: