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
Given these nginx instances are configured to run in containers, is there any reason that port_in_redirect off; should not be a default directive in the server {} block? I realize one can add that directive to a file in ./nginx-default-cfg/, but given the unlikely scenario of wanting the internal container listening port exposed by a redirect it seems reasonable to disable by default.
Scenario: foo.org/blah =[redirect]=> foo.org:8080/blah/, which will fail because haproxy (or the like) isn't listening to 8080.
The text was updated successfully, but these errors were encountered:
Given these nginx instances are configured to run in containers, is there any reason that
port_in_redirect off;
should not be a default directive in theserver {}
block? I realize one can add that directive to a file in./nginx-default-cfg/
, but given the unlikely scenario of wanting the internal container listening port exposed by a redirect it seems reasonable to disable by default.Scenario: foo.org/blah =[redirect]=> foo.org:8080/blah/, which will fail because haproxy (or the like) isn't listening to 8080.
The text was updated successfully, but these errors were encountered: