LINUX.ORG.RU

История изменений

Исправление beastie, (текущая версия) :

PPS: https://docs.nginx.com/nginx/admin-guide/web-server/web-server/#nginx-location-priority

  1. Test the URI against all prefix strings.
  2. The = (equals sign) modifier defines an exact match of the URI and a prefix string. If the exact match is found, the search stops.
  3. If the ^~ (caret-tilde) modifier prepends the longest matching prefix string, the regular expressions are not checked.
  4. Store the longest matching prefix string.
  5. Test the URI against regular expressions.
  6. Stop processing when the first matching regular expression is found and use the corresponding location.
  7. If no regular expression matches, use the location corresponding to the stored prefix string.

Учитывая все «search stops» и «not checked» результирует в «first most specific (longest) match wins» IIRC, поэтому оно у тебя и ниже в конфиге не работает.

Исправление beastie, :

PPS: https://docs.nginx.com/nginx/admin-guide/web-server/web-server/#nginx-location-priority

  1. Test the URI against all prefix strings.
  2. The = (equals sign) modifier defines an exact match of the URI and a prefix string. If the exact match is found, the search stops.
  3. If the ^~ (caret-tilde) modifier prepends the longest matching prefix string, the regular expressions are not checked.
  4. Store the longest matching prefix string.
  5. Test the URI against regular expressions.
  6. Stop processing when the first matching regular expression is found and use the corresponding location.
  7. If no regular expression matches, use the location corresponding to the stored prefix string.

Учитывая все «search stops» и «not checked» результирует в «first most specific (longest) match wins», поэтому оно у тебя и ниже в конфиге не работает.

Исправление beastie, :

PPS: https://docs.nginx.com/nginx/admin-guide/web-server/web-server/#nginx-location-priority

  1. Test the URI against all prefix strings.
  2. The = (equals sign) modifier defines an exact match of the URI and a prefix string. If the exact match is found, the search stops.
  3. If the ^~ (caret-tilde) modifier prepends the longest matching prefix string, the regular expressions are not checked.
  4. Store the longest matching prefix string.
  5. Test the URI against regular expressions.
  6. Stop processing when the first matching regular expression is found and use the corresponding location.
  7. If no regular expression matches, use the location corresponding to the stored prefix string.

Учитывая все «search stops» и «not checked» результирует в «fist most specific (longest) match wins», поэтому оно у тебя и ниже в конфиге не работает.

Исходная версия beastie, :