Renaming one of the params to fly around an nginx bug
This commit is contained in:
parent
b86c797109
commit
c6459aabab
1 changed files with 2 additions and 2 deletions
|
|
@ -17,7 +17,7 @@
|
|||
|
||||
# If we receive X-Forwarded-Proto, pass it through; otherwise, pass along the
|
||||
# scheme used to connect to this server
|
||||
map $http_x_forwarded_proto $proxy_x_forwarded_proto {
|
||||
map $http_x_forwarded_proto $default_forwarded_proto {
|
||||
default $http_x_forwarded_proto;
|
||||
'' $scheme;
|
||||
}
|
||||
|
|
@ -26,7 +26,7 @@ map $http_x_forwarded_proto $proxy_x_forwarded_proto {
|
|||
# pass along the original value.
|
||||
map $http_cloudfront_forwarded_proto $proxy_x_forwarded_proto {
|
||||
default $http_cloudfront_forwarded_proto;
|
||||
'' $proxy_x_forwarded_proto;
|
||||
'' $default_forwarded_proto;
|
||||
}
|
||||
|
||||
# If we receive Upgrade, set Connection to "upgrade"; otherwise, delete any
|
||||
|
|
|
|||
Loading…
Reference in a new issue