问题原文
原帖链接 · tompave · CC BY-SA 3.0
In my nginx 1.12.2 conf file, I have:
upstream app {
server unix:/tmp/app.sock fail_timeout=0;
}
server {
listen 443 deferred;
root /some/dir;
try_files $uri @app;
# If the request is for the naked domain, just serve the index bundle
# without going through Rails
#
location = / {
try_files /index.html =404;
}
# If the request if for the /api prefix, go directly to Rails.
# This location block is not strictly required, but it could be a handy
# customization hook for extra headers and settings.
#
location /api/ {
# Extra conf!
try_files @app;
}
# The location directory allows very creative configurations.
# http://nginx.org/en/docs/http/ngx_http_core_module.html#location
#
# This is just a named location to be used in try_files.
location @app {
proxy_pass_request_headers on;
proxy_set_header ...
proxy_pass http://app;
}
}
There, this is not really right because it has a single argument:
location /api/ {
# Extra conf!
try_files @app;
}
...but it communicates well what I'm trying to achieve.
I suppose I could get try_files to work by adding a non-esitent file before the last argument.
Is try_files the only way to do it, or is there another more idiomatic directive?
已采纳解答
原帖链接 · Richard Smith · CC BY-SA 4.0
Your scheme will not work. When nginx settles on the final location block to process the request, it will use the "settings and headers" that are in scope, which may be inherited from a surrounding block, but will not include any "extra headers and settings" from sibling blocks - irrespective of the process taken to find the final location block. See request_processing docs for more.
If you have common statements applicable to a number of locations, you can offload them to a separate file and include them where necessary. For example:
location / {
try_files $uri @app;
}
location /api/ {
# Extra conf!
include my/proxy/conf;
}
location @app {
include my/proxy/conf;
}
See include doc for more.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
