Configure EWA to work with proxy servers and load balancers

In your appsettings.json file remove the under score from the _ForwardedHeadersOptions option.

Before

CODE

"_ForwardedHeadersOptions": {
    "Enabled": true,
    "RequestLogging": false
	}

After

CODE

"ForwardedHeadersOptions": {
    "Enabled": true,
    "RequestLogging": false
	}

Enabling this option will enable the EzeScan WebApps Middleware to handling the following headers:

Header	Description
X-Forwarded-For	Holds information about the client that initiated the request and subsequent proxies in a chain of proxies. This parameter may contain IP addresses (and, optionally, port numbers). In a chain of proxy servers, the first parameter indicates the client where the request was first made. Subsequent proxy identifiers follow. The last proxy in the chain isn't in the list of parameters. The last proxy's IP address, and optionally a port number, are available as the remote IP address at the transport layer.
X-Forwarded-Proto	The value of the originating scheme (HTTP/HTTPS). The value may also be a list of schemes if the request has traversed multiple proxies.
X-Forwarded-Host	The original value of the Host header field. Usually, proxies don't modify the Host header.