Populate RemoteIpAddress and RemotePort on HttpContext.Connection #89
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #22
Allows the AspNetCore application to access the remote client ip/port information via HttpContext.Connection, which works when running locally via
dotnet run
.RemoteIpAddress is obtained from the APIGatewayProxyRequest's RequestContext.Identity.SourceIp
RemotePort is obtained from the APIGatewayProxyRequest's Headers["X-Forwarded-Port"]
For example this would allow for a WebAPI Controller to use the remote info:
Updated the test input to provide the source IP, did not add the header "X-Forwarded-Port" in case a better place to get port information from is known by the maintainer.