ASP.NET Core: Losing Client IP After nginx Reverse Proxy

Sep 5, 2024#ASP.NET Core #ABP #nginx58

AI Translation

This post is translated from Chinese into English through AI.View Original

AI-generated summary

To configure Nginx as a reverse proxy, add the specified server block to your Nginx configuration, which includes directives for passing headers like the client's IP and protocol. After modifying the configuration, remember to reload Nginx with `nginx -s reload`. In your ASP.NET Core application, include middleware to handle forwarded headers, allowing you to retrieve the client's IP correctly.

Add the following directive in the nginx website configuration:

server {

    # reverse proxy
    location / {
        proxy_pass            http://127.0.0.1:5000;

        proxy_set_header Host $host;
        proxy_set_header X-Real-IP         $remote_addr;
        proxy_set_header Forwarded         $proxy_add_forwarded;
        proxy_set_header X-Forwarded-For   $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header X-Forwarded-Host  $host;
        proxy_set_header X-Forwarded-Port  $server_port;
    }
}

Remember to nginx -s reload after modifying the nginx configuration.

Add the following middleware in the ASP.NET Core program:

app.UseForwardedHeaders(new ForwardedHeadersOptions
{
    ForwardedHeaders = ForwardedHeaders.XForwardedFor | ForwardedHeaders.XForwardedProto
});

After the configuration is complete, you can obtain the client IP in the original way, and the middleware will handle the adaptation issues properly.