RemoteIpAddress

[heapstack-developer]

Hi,

The description about HttpContext.Connection.RemoteIpAddress is a little bit confusing. I would suggest putting an example of how it exactly works including also the options.ForwardLimit.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: e548cd16-b06c-5802-a1a7-c627167857ae
• Version Independent ID: c48abb08-bea3-dcff-c067-2edf5dc9b3a6
• Content: Configure ASP.NET Core to work with proxy servers and load balancers
• Content Source: aspnetcore/host-and-deploy/proxy-load-balancer.md
• Product: aspnet-core
• Technology: aspnetcore-hostdeploy
• GitHub Login: @Rick-Anderson
• Microsoft Alias: riande

[Rick-Anderson]

@Tratcher please review

[Tratcher]

Yeah, it's a complicated flow and an execution example would help. There's the start of one here that shows the setup: https://github.com/dotnet/AspNetCore.Docs/blob/master/aspnetcore/host-and-deploy/proxy-load-balancer.md#forwarded-headers-middleware-options (I'm ignoring the X-Forwarded-For-My-Custom-Header-Name setting...)

Next you'd need to specify the initial values for RemoteIpAddress, Scheme, and Host (127.0.10.1, http, and internalhost). These represent the connection to the most immediate proxy.

Now you need some headers: X-Forwarded-For: 1.1.1.1, 2.2.2.2, 3.3.3.3 X-Forwarded-Proto: https, http X-Forwarded-Host: publicdomain.org, middletier.mydomain

Now for the flow:

• The middleware processes entries in sets, right to left.
• The first set is the initial conditions (127.0.10.1, http, and internalhost). 127.0.10.1 is on the KnownProxies list so we trust it and continue.
• The next set is 3.3.3.3,http, mymiddltier.mydomain. 3.3.3.3 is not on the KnownProxies list so processing stops and these values get assigned to RemoteIpAddress, Scheme, and Host.

If I added 3.3.3.3 to the KnownProxies list then it would have continued on to the next set.

• The next set is 2.2.2.2, https, publicdomain.org. Now we hit two stops, 2.2.2.2 isn't on the KnownProxies list and we've hit the ForwardLimit of 2, so these values are assigned to the request and processing stops.

Also note that values are removed from the x-forwarded- headers as they're processed, and old values are stored in x-original- headers.