nginx error_page重定向固定标头

发布于 2025-01-24 05:50:27 字数 1448 浏览 0 评论 0原文

我正在尝试编写用于身份验证的NGINX配置，但是我不确定在使用302重定向时如何保留标头。

以下是如何设置服务器的示例。

location / {
    #send to /auth/ for authentication
    request_auth /auth/;
    #upon failure, redirect to login
    error_page 401 404 = @noaccess;

    ...
}

location @noaccess {
    return 302 /login/;
}

location /auth/ {
    internal;
    proxy_pass http://127.0.0.1:8888/;
    proxy_pass_request_body off;
    proxy_set_header Content-Length "";
    #The header set here is what I would like to retain
    proxy_set_header X-Original-URI $request_uri;
}

location /login/ {
    proxy_pass http://127.0.0.1:9000/;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    #by the time 302 redirect, $request_uri is no longer the original...
    proxy_set_header X-Target $request_uri;
}

本质上，必须首先在/auth/位置进行身份验证服务器的所有请求。这个位置通常将拥有我在其子请求中关心的$ request_uri。但是，每当requeset_auth指令失败时，我们都会与@noaccess位置重定向，nginx向/login/login/code>>>>。我有没有办法保留原始的$ request_uri，以便将其作为标头发送到/login/login/位置？（这是为了稍后在成功身份验证后进行重定向而需要的）。

我已经看到一些用户谈论auth_request_set 指令，但老实说，我不明白如何有效使用它以及如何重命名或可用。

原文

I am trying to write an nginx configuration for authentication, but I am unsure of how to retain headers when using a 302 redirect.

Below is an example of how the server is setup.

location / {
    #send to /auth/ for authentication
    request_auth /auth/;
    #upon failure, redirect to login
    error_page 401 404 = @noaccess;

    ...
}

location @noaccess {
    return 302 /login/;
}

location /auth/ {
    internal;
    proxy_pass http://127.0.0.1:8888/;
    proxy_pass_request_body off;
    proxy_set_header Content-Length "";
    #The header set here is what I would like to retain
    proxy_set_header X-Original-URI $request_uri;
}

location /login/ {
    proxy_pass http://127.0.0.1:9000/;
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
    #by the time 302 redirect, $request_uri is no longer the original...
    proxy_set_header X-Target $request_uri;
}

Essentially all requests to the server must first be authenticated in the /auth/ location. This location will generally possess the $request_uri that I care about in its sub request. However, whenever the requeset_auth directive fails, and we are redirected with the @noaccess location, nginx makes a new request to /login/.
Is there a way for me to retain the original $request_uri such that it is sent as a header to the /login/ location? (this is needed in order to do a redirect later upon successful authentication).

I've seen some users talk about the auth_request_set directive, but I honestly do not understand how to use it effectively and how the headers of the sub request are renamed or made available.

分享到QQ

分享到微博