如何使用 NGINX 缓存 NextJS 10.0 图像

本文介绍了如何使用 NGINX 缓存 NextJS 10.0 图像的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！

问题描述

我们想使用 NGINX 启动 NextJS 10 应用程序，因此我们使用类似于以下内容的配置:

We would like to launch a NextJS 10 app using NGINX so we use a configuration similar to:

location /_next/static/ {
    alias /home/ec2-user/my-app/.next/static/;
    expires 1y;
    access_log on;
}

效果很好，它可以将我们的静态数据缓存一年，但是当我们使用 NextJS 图像时我未能在动态调整大小的图像上添加 expires 标签.

It works great, it caches for a year our statics but as we use NextJS images I'm failing to add an expires tag on on-the-fly resized images.

如果我这样做:

location /_next/image/ {
    alias /home/ec2-user/my-app/.next/image;
    expires 1y;
    access_log on;
}

它只是在图像上返回 404.

It just returns a 404 on images.

这是我的服务器部分 NGINX 配置:

Here is my server part NGINX config :

server {
    listen 80;
    server_name *.my-website.com;
    # root        /usr/share/nginx/html;
    # root /home/ec2-user/my-app;
    charset     utf-8;

    client_max_body_size    20M;
    client_body_buffer_size 20M;

    proxy_connect_timeout    600;
    proxy_send_timeout       600;
    proxy_read_timeout       600;
    send_timeout             600;

    underscores_in_headers on;

    add_header X-Frame-Options SAMEORIGIN always;
    add_header X-Content-Type-Options nosniff always;
    add_header X-XSS-Protection "1; mode=block" always;
    add_header Referrer-Policy "same-origin" always;

    location = /robots.txt {
        proxy_pass https://api.my-website.com/robots.txt;
    }

    location /_next/static/ {
        alias /home/ec2-user/my-app/.next/static/;
        expires 1y;
        access_log on;
    }

    location / {
        # reverse proxy for merchant next server
        proxy_pass http://localhost:3000;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_pass_request_headers      on;
        proxy_cache_bypass $http_upgrade;
        proxy_buffering off;
    }
}

推荐答案

这里是一个示例，您可以如何依赖上游 Content-Type 标头来设置 Expires和 Cache-Control 标头:

Here is an example how you can rely of upstream Content-Type header to set up the Expires and Cache-Control headers:

map $upstream_http_content_type $expire {
    ~^image/    1y; # 'image/*' content type
    default     off;
}
server {
    ...
    location / {
        # reverse proxy for merchant next server
        proxy_pass http://localhost:3000;
        ...
        expires $expire;
    }
}

与您可以为任何其他内容类型的代理响应调整缓存控制标头的方式相同.$upstream_http_ nginx 变量在here中描述.

The same way you can tune cache control headers for any other content type of proxied response. The $upstream_http_<name> nginx variable is described here.

更新

要仅通过特定 URI 添加缓存控制标头，您可以使用两个链接的 map 块:

To add cache control headers only by specific URIs you can use two chained map blocks:

map $uri $expire_by_uri {
    ~^/_next/image/    1y;
    default            off;
}
map $upstream_http_content_type $expire {
    ~^image/           $expire_by_uri;
    default            off;
}

如果除了来自 /_next/image/... URI 的图像之外，你什么都不期待，你可以使用

And if you don't expect anything but the images from /_next/image/... URIs, you can just use the

map $uri $expire {
    ~^/_next/image/    1y;
    default            off;
}

这篇关于如何使用 NGINX 缓存 NextJS 10.0 图像的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！

Headers