-
-
Notifications
You must be signed in to change notification settings - Fork 440
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
Fixed Magento not detecting HTTPS behind a proxy. #1081
Fixed Magento not detecting HTTPS behind a proxy. #1081
Conversation
This fix adds a check for the "HTTP_X_FORWARDED_PROTO" header to determine if the scheme is HTTPS or HTTP.
As far as i can see, both classes inherit from Zend_Controller_Request_Http. So it might be better to do these changes in this class to avoid duplicate code. |
Thank @kkrieger85, I have now moved the fix into the class that you suggested :-) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice. Less code.
LGTM
@kkrieger85 is it possible to use "squash merge" option for unified commit log? |
Of course, it is
Am Do., 23. Juli 2020 um 15:53 Uhr schrieb sv3n <notifications@github.com>:
… @kkrieger85 <https://github.com/kkrieger85> is it possible to use "squash
merge" option for unified commit log?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1081 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABB24Q6SJ2RJK2ZCKITGAPDR5A6EZANCNFSM4OMO55CA>
.
|
can confirm of one case, where this did work and solve related Issues, thank you for providing the patch 😀 |
Fixes Magento not detecting HTTPS behind a proxy.
Fixes Magento not detecting HTTPS behind a proxy.
This fix adds a check for the "HTTP_X_FORWARDED_PROTO" header to determine if the scheme is HTTPS or HTTP.