大网数据广告活动
服务器运维问答

nginx different routes for / and /*

· 52CE 我爱测

I'd like to route / to a.sock and /(.*) to b.sock . I tried location / { proxy_pass http://unix:/tmp/a.sock; proxy_read_timeout 30; proxy_connect_timeout 30; proxy_redirect off; proxy_set_header Host $host; proxy_set_header X-Rea…

问题原文

原帖链接 · Darko · CC BY-SA 4.0

I'd like to route / to a.sock and /(.*) to b.sock.

I tried

    location / {
        proxy_pass http://unix:/tmp/a.sock;
        proxy_read_timeout 30;
        proxy_connect_timeout 30;
        proxy_redirect off;
        proxy_set_header Host               $host;
        proxy_set_header X-Real-IP          $remote_addr;
        proxy_set_header X-Forwarded-For    $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto  $scheme;
    }
    location ~ /(.*) {
        proxy_pass http://unix:/tmp/b.sock;
        proxy_read_timeout 30;
        proxy_connect_timeout 30;
        proxy_redirect off;
        proxy_set_header Host               $host;
        proxy_set_header X-Real-IP          $remote_addr;
        proxy_set_header X-Forwarded-For    $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto  $scheme;
    }

with different ordering too.

Can this be achived with nginx, if so, how?

My take is, according to the documentation anything ending with a / assumes a wildcard after the / and the plain route without the regex takes precedence.

Essentially the backend on b.sock has a route definition of /:term or /{term} depending on which routing lib you use, but has no handler for /. You're probably thinking "so add a handler for / and call it a day". I might do that, but it's a workaround. I would like a.sock to handle /.

So again, can this be done with nginx and how?

已采纳解答

原帖链接 · Danila Vershinin · CC BY-SA 4.0

Use exact matching for homepage, e.g. location = / { … }. The location / { … } will apply for the rest of the pages.

The exact matching (with equals sign) has priority over prefix location (no equals sign).

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2021-11-14)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。