10
votes
var test1 = HttpContext.Features.Get<IHttpConnectionFeature>();
var test2 = HttpContext.Connection.RemoteIpAddress;

When running the application locally on IISExpress, these two lines correctly return the value 0:0:1.

When I publish the application on IIS 7.5 (which is running on a VM). RemoteIpAddress is always null

I am using ASP.Net 5 RC 1.

How can I get the client's IP address in an ASP.NET 5 application ?

I tried the solutions in the following questions, however I have the problem mentioned above:

3
The X-Forwarded-For appears to be set by default in RC1 U1 from this Answer - crokusek

3 Answers

12
votes

What you're seeing is accurate, if not useful. Connections termination at IIS, which then forwards to Kestrel, the v.next web server, so connections to the web server are indeed from localhost.

What you need to do is enable support for X-Forwarded-For

  1. Add the Microsoft.AspNet.HttpOverrides package
  2. In your Configure() method add

        app.UseOverrideHeaders(new OverrideHeaderMiddlewareOptions
        {
            ForwardedOptions = ForwardedHeaders.XForwardedFor | 
                               ForwardedHeaders.XForwardedProto
        });
    

Note that this package will change in RC2 to make it safer to use.

8
votes

In ASP.NET Core 2.0 project you need to add package Microsoft.AspNetCore.HttpOverrides and add this code to your Configure method:

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

That is because of you are trying to connect from localhost. If you have another computer in same LAN, try to connect with this pc but use user ip instead of localhost.