Understand NGINX location priority before adding another regex

For NGINX location priority, the safest approach is a bounded operational change, not a command pasted without context. This runbook starts with effective state, shows the smallest candidate action, and finishes by repeating the real user or system path.

TL;DR: NGINX first finds the longest prefix location and then evaluates regular expressions under documented rules, with exact and nested matches changing the search path. Capture a baseline with sudo nginx -T, make the reviewed change only when the evidence matches, then verify with curl -v https://app.example.com/example/path and keep the rollback ready.

Audience: web operators who can identify the active NGINX configuration, upstream service, and external request path. This guide assumes familiarity with NGINX and TLS and a change window appropriate to the system.

The direct answer

Representative URIs select the intended handler, upstream, headers, and filesystem path. That is the success condition for NGINX location priority; command completion by itself is not enough.

The important boundary is client TLS, virtual server selection, location matching, request transformation, upstream connection, and response delivery. NGINX first finds the longest prefix location and then evaluates regular expressions under documented rules, with exact and nested matches changing the search path. If an observation does not identify which side of that boundary failed, collect a narrower observation before changing state.

How the mechanism works

For NGINX location priority, use this mental model: NGINX selects a listener and virtual server, chooses a location, applies phase handlers, connects to an upstream when configured, and streams or buffers the response. The model prevents a common mistake—treating configuration text, control-plane acceptance, process state, and end-user behavior as the same proof.

Follow four stages:

1. Observe: identify the exact host, object, version, owner, and active configuration.
2. Interpret: write the expected result, the abnormal result, and what would remain inconclusive.
3. Change: apply one reviewed action at the narrowest layer that contradicts the baseline.
4. Verify: repeat the original path and compare the same evidence, including adjacent safety controls.

Preflight and safety boundary

Keep the current worker generation serving traffic, test the complete configuration, and retain a direct upstream check before reloading proxy or TLS changes.

Before NGINX location priority, record UTC time, the current version or digest, the exact target, recent changes, and who owns the workload. The rollback for this runbook is: restore the previous location block, test, reload, and replay a path matrix that includes positive and negative cases.

Do not continue if the target identity is ambiguous, the current state cannot be saved, the only recovery session would be at risk, or the proposed command affects more objects than the brief names.

Capture the read-only baseline

Run these commands one at a time. Replace example names and addresses deliberately; do not paste production secrets into a transcript.

sudo nginx -T
rg -n 'location[ =^~*]' /etc/nginx
curl -v https://app.example.com/example/path

Interpret the baseline before moving on:

• Expected: representative URIs select the intended handler, upstream, headers, and filesystem path.
• Abnormal: a regex shadows the prefix, an alias changes path mapping, or another server block owns the request.
• Inconclusive: missing output can also mean the wrong context, permissions, namespace, log window, binary, or target. Prove those assumptions before treating absence as health.

Save the decisive output, exit status, and timestamp. Redact credentials, customer data, private topology, tokens, and complete environment dumps.

Apply the smallest candidate change

The following is state-changing example syntax, not an instruction to run it unchanged:

sudo nginx -t
sudo systemctl reload nginx

For NGINX location priority, the proposed change is acceptable only when the read-only baseline predicts its effect and the rollback is available. The key risk is: adding ^~ or a broad regex can fix one URI while rerouting an entire application subtree.

Prefer an immutable artifact, validated configuration, dry-run, transaction, candidate object, or staged target when the tool supports one. Record the exact command and UTC time so later telemetry can be correlated to the change.

Verify the result from the outside in

curl -v https://app.example.com/example/path
curl -v https://app.example.com/example/other
sudo tail -n 50 /var/log/nginx/access.log

Verification for NGINX location priority has three layers:

1. The control plane or command reports the intended effective state.
2. The process, resource, or data path reflects that state without a new pressure signal.
3. The original user-visible or dependent-system path succeeds from an independent vantage point.

If curl -v https://app.example.com/example/path succeeds but the original path still fails, stop. The change may have repaired a local symptom while DNS, policy, routing, caching, dependency, or client state remains broken.

Failure branches

The baseline does not match this runbook

When a regex shadows the prefix, an alias changes path mapping, or another server block owns the request, do not force the candidate command. Return to identity and scope, compare a healthy peer only through effective settings, and name a new falsifiable mechanism.

The change succeeds but behavior does not

A successful sudo nginx -t proves that one interface accepted a request. It does not prove convergence, readiness, data compatibility, external routing, or client recovery. Re-run the same evidence at each downstream boundary.

The change makes the system worse

Execute the written rollback: restore the previous location block, test, reload, and replay a path matrix that includes positive and negative cases. Preserve the failed candidate and relevant logs long enough to explain the outcome; do not destroy the evidence with broad cleanup or repeated restarts.

Operator checklist

• Confirm the exact target, context, identity, version, and active owner.
• Capture the read-only baseline and one disconfirming observation.
• Label sudo nginx -t as state-changing during review.
• Keep recovery access and rollback independent of the path being edited.
• Change one layer, record UTC time, and wait for its real convergence boundary.
• Verify the original path, adjacent controls, resource pressure, and persistence.
• Update the runbook when observed behavior differs from the source-reviewed model.

Investigate it in Tryssh

$ curl -v https://app.example.com/example/path
Expected: representative URIs select the intended handler, upstream, headers, and filesystem path.

Tryssh can preserve this evidence loop and show a state-changing command for human approval. It does not make the operator's identity, recovery access, rollback, or platform authority decisions.

Evidence and review status

This NGINX location priority runbook was source-reviewed on 2026-07-29 against current first-party documentation. The commands are illustrative and use example targets. The page does not claim that the change was reproduced across every distribution, managed service, version, network, or workload.

Limitations and trade-offs

Adding ^~ or a broad regex can fix one URI while rerouting an entire application subtree. Managed platforms may generate configuration, restrict privileges, replace local state, or expose a different control plane than the upstream project. Confirm the installed version and provider contract before applying a repair.

Search visibility is not proof of operational correctness. Treat this page as a decision aid, preserve independent recovery, and stop when the evidence contradicts its assumptions.

Related operator runbooks

Continue with NGINX proxy timeouts, nginx test config reload, the NGINX and TLS foundation guide, and the SSH hardening checklist.

Sources and further reading

• NGINX location priority first-party reference
• NGINX documentation
• NGINX proxy module
• NGINX log module