The HTTP Listener configuration category includes the following configurable options:
Bind Address
Context Path
Endpoint Health Path
Unhealthy Status Code
HTTPS Forwarding Assumed
Listener Port
Respect Forward Headers
|
Bind Address |
|
|
STRING | |
The local network interface address to bind to. Set to 0.0.0.0 to bind to all addresses.
|
|
|
|
0.0.0.0
|
|
|
|
Context Path |
|
|
STRING | |
This setting provides the path at the given port that this server will listen on. By default the server simply listens at the / path, but this could be changed to a sub-path for some network architectures. For example, if a reverse proxy is proxying the server but also serving other endpoints with the same port at different paths, this setting can be used as a hint to this server as to which path should be used. If a reverse proxy is serving this server in such a way that a request to the proxy at /baseurl/foo/index.html should map to /index.html on this server, you should put /baseurl/foo as the context root.
|
|
|
|
/
|
|
|
|
Endpoint Health Path |
|
|
STRING | |
Specifies a path (in the form /path/to/endpoint ) that will be used as the Endpoint Health Check path. See Endpoint Health for information on this feature.
|
|
|
|
/endpoint-health
|
|
|
|
Unhealthy Status Code |
|
|
POSITIVE_INTEGER | |
Status code to return if any Health Checks are unhealthy. | |
|
|
200
|
|
|
|
HTTPS Forwarding Assumed |
|
|
BOOLEAN | |
If enabled, the server will treat incoming requests as though they were secure even if they are not. This is useful in order to force redirects to use HTTPS in environments where the X-Forwarded-Proto does not reliably get passed from network infrastructure in front of Smile CDR to Smile CDR.
|
|
|
|
false
|
|
|
|
Listener Port |
|
|
POSITIVE_INTEGER | |
The TCP port on which this module listens. | |
|
|
(no default) | |
|
|
Respect Forward Headers |
|
|
BOOLEAN | |
If enabled, the server will respect values provided by the client in the HTTP Forward , X-Forwarded-For , X-Forwarded-Host , and X-Forwarded-Proto headers. These headers are useful in cases where Smile CDR is being served behind a reverse proxy. This setting should be disabled if the server is not behind a proxy since this could allow clients to masquerade their source IP, which is a security risk. See Respecting Forward Headers for more information.
|
|
|
|
false
|
|
|