RemoteIpAddress is always null

谁说我不能喝 提交于 2019-11-30 03:51:55

问题


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:

  • Question 1
  • Question 2

回答1:


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.




回答2:


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
});



回答3:


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.



来源:https://stackoverflow.com/questions/35441521/remoteipaddress-is-always-null

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!