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
Current Behaviour: mup constructs VIRTUAL_HOST based on proxy.domains. Nginx creates rules that are inconsistent with domain redirect. Consider a scenario where proxy.domains contain both non-www and www. Now Nginx constructs server blocks separately for non-www and www. Now https://example.com and https://www.example.com becomes valid. Presently it is impossible to override Nginx default.conf with shared proxy config
Expected Behaviour: separating HOST enable user to use redirect method in Nginx for a single canonical name
The text was updated successfully, but these errors were encountered:
Mup version (
mup --version
): 1.4.5VIRTUAL_HOST needs to be decoupled from LETSENCRYPT_HOST so that we see a consistent url in address bar
Where is VIRTUAL_HOST used?
For configuring jwilder/nginx-proxy
Why is VIRTUAL_HOST used?
jwilder/nginx-proxy uses this environment variable to create default.conf rules
Please refer: https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/Choosing_between_www_and_non-www_URLs
Current Behaviour: mup constructs VIRTUAL_HOST based on proxy.domains. Nginx creates rules that are inconsistent with domain redirect. Consider a scenario where proxy.domains contain both non-www and www. Now Nginx constructs server blocks separately for non-www and www. Now https://example.com and https://www.example.com becomes valid. Presently it is impossible to override Nginx default.conf with shared proxy config
Expected Behaviour: separating HOST enable user to use redirect method in Nginx for a single canonical name
The text was updated successfully, but these errors were encountered: