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

Nginx Try_Files to create local content cache?

· 52CE 我爱测

I'm trying to either serve images locally, or from a share (locally refreshed overnight). My nginx site is served across 2 or more servers, to keep all the content in sync across each server, I'm storing it in an Azure file share…

问题原文

原帖链接 · Stuart.Sklinar · CC BY-SA 3.0

I'm trying to either serve images locally, or from a share (locally refreshed overnight).

My nginx site is served across 2 or more servers, to keep all the content in sync across each server, I'm storing it in an Azure file share, and that's the location root (/mnt/wp).

This works pretty well (along with Nginx Caching), but the images have a pretty slow wait time, which I assume is a latency issue client-server-azure. So to make things faster, I'd like to serve the images locally (/var/www/), if available, then fall back to azure (/mnt/wp)

So far I've got this location block, but the logs are showing a redirect loop..

Am I missing something?

   location /wp-content/ {
            add_header X-uploads $uri;
            try_files @contentCache/$uri $uri;
    }

    location @contentCache{
            root /var/www;
    }

已采纳解答

原帖链接 · Richard Smith · CC BY-SA 3.0

Your syntax for try_files is wrong. A named location should be the default action placed in the last element. Something like this:

location /wp-content/ {
    ...
    try_files $uri @contentCache;
}
location @contentCache {
    ...
    try_files $uri =404;
}

See this document for more.

If you need to reverse the order, just swap around your root directives.

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

资料来源与适用范围

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

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

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