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
I suspect that when nginx got a http request, it tries to redirect before the $proxy_upstream_name variable is set. The generated nginx config seems to confirm so:
# enforce ssl on server side
if ($pass_access_scheme = http) {
return 301 https://$best_http_host$request_uri;
}
location / {
set $proxy_upstream_name "www-www-5000";
The text was updated successfully, but these errors were encountered:
cheungpat
added a commit
to cheungpat/ingress-nginx
that referenced
this issue
May 14, 2017
When nginx performs ssl redirect, $proxy_upstream_name used in log
is not initialized because it is set after nginx matched a location directive,
which is not the case when performing a ssl redirect.
refs kubernetes#711
When nginx performs ssl redirect, $proxy_upstream_name used in log
is not initialized because it is set after nginx matched a location directive,
which is not the case when performing a ssl redirect.
refs kubernetes#711
(Cherry-picked from a83f17c and adjusted to keep the settings in logical order)
It appears that when there is a 301 Redirect, nginx prints this log:
Tested it with curl:
I suspect that when nginx got a http request, it tries to redirect before the
$proxy_upstream_name
variable is set. The generated nginx config seems to confirm so:The text was updated successfully, but these errors were encountered: