Differences

This shows you the differences between two versions of the page.

--- wiki:nginx_troubleshooting [2023/09/07 13:28] – add Location matching when serving content antisa
+++ wiki:nginx_troubleshooting [2023/10/03 11:18] (current) – [Location matching when serving content] add help box antisa
@@ Line 30: / Line 30: @@
   * it could be that the //server_name// is not defined or there's a typo
   * pay attention to http vs. https and redirects; if you get redirected from http to https and this is not what you want, redirect could be done by some proxied app (for example wordpress might do this via its WP_HOME and WP_SITEURL variables) and then the request will happen to 443 port on which nginx will serve the first vhost that is listening on this port and the //server_name// matches, so if your b.example.com vhost does not listen on 443 as well you might get the configuration from some other vhost which does listen on 443 which will confuse you.
+  * Also listen directive gives precedence to IP:PORT than to only PORT, so nginx might serve for example wrong certificates (i.e. self-signed ones) if there is a config like
+<code nginx>
+listen 1.2.3.4:443 ssl;
+server_name de_verticals_upstream;
+ssl_certificate     /etc/ssl/server.crt;
+...
+</code>
+and somewhere else you have
+<code nginx>
+...
+listen 443 ssl;
+...
+</code>
 ===== Location matching when serving content =====
@@ Line 63: / Line 78: @@
 </code>
+So modifier priority matching is as follows:
+. `=`       Exact match, terminate immediately
+. `^~`      Longest-prefix-match (not regex!)
+. `~`, `~*` Regular expression case sensitive/insensitive
+. `/`       Longest-prefix-match
+<WRAP center round help 60%>
+If you are using the grouping of URIs in parenthesis e.g.
+  location ^~ /(.well-known|pathA|otherslug)
+This won't work. Use the `~*` modifier for that.
+</WRAP>
 ==== Tested on ====