如何简化并缩短现有NGINX Rewrite规则？

Great question! Those 6 rules definitely get repetitive, especially since they all point to the same page.php endpoint with different parameter combinations. Let's break down how to simplify this while fixing a subtle order issue in your original config.

First, Fix the Order Problem (Critical!) #

Your original rules have a bug: the first rule rewrite ^/([^/]+)/?$ /page.php?a=$1 last; matches all single-segment paths (including numbers like /123/ and fixed values like /a/), which means the next two rules for b and c will never actually run. We need to handle special cases first before the generic a parameter.

Simplified Rule Set (3 Rules Total) #

Here's how to condense your 6 rules into 3, while covering all parameter combinations:

# Handle single-segment numeric paths (only b parameter)
rewrite ^/([0-9]+)/?$ /page.php?b=$1 last;

# Handle single-segment fixed values (only c parameter)
rewrite ^/(a|b)/?$ /page.php?c=$1 last;

# Handle all paths starting with a generic value (a alone, a+b, a+c, a+b+c)
rewrite ^/([^/]+)(?:/([0-9]+))?(?:/(a|b))?/?$ /page.php?a=$1&b=$2&c=$3 last;

How This Works #

Let's break down the third rule, which does the heavy lifting:

• ^/([^/]+): Captures the first segment as the a parameter (matches any non-slash characters)
• (?:/([0-9]+))?: Optional second segment (numeric) captured as b — the ?: makes this a non-capturing group for the slash, so only the number goes into $2
• (?:/(a|b))?: Optional third segment (fixed a/b values) captured as c
• /?$: Allows an optional trailing slash for consistency

When a segment isn't present (e.g., only a is used), the corresponding variable ($2 or $3) will be empty, and NGINX will just omit the empty parameter from the request (or pass it as an empty string, which page.php can handle the same way as your original rules).

Why This Is Better #

• Fewer rules: 3 instead of 6, making your config cleaner and easier to maintain
• Fixes the original order bug: Special cases (numeric b, fixed c) are processed first, so they don't get swallowed by the generic a rule
• Scalable: If you ever need to add more optional parameters (e.g., a d parameter), you can just extend the third rule instead of adding new rewrite lines

内容的提问来源于stack exchange，提问作者Toleo