AllowForwardHeaders

What kind of forward header parsing are we allowing.

Name

Description

NONE

No parsing shall be performed.

FORWARD

Only process the standard Forward header as defined by For more info see: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Forwarded

X_FORWARD

Only process the non standard but widely used X-Forward-* headers.

These headers are not official standards but widely used. Users are advised to avoid them for new applications.

ALL

Will process both and . Be aware that mixing the 2 headers can open security holes has specially crafted requests that are not validated as proxy level can allow bypassing the proxy desired forward value.

For example, a proxy will add the X-Forward-* headers to a request but not filter out if the original request includes the Forward header.

LoggerFormat

The possible out of the box formats.

Name

Description

DEFAULT

remote-client - - [timestamp] "method uri version" status content-length "referrer" "user-agent"

SHORT

remote-client - method uri version status content-length duration ms

TINY

method uri status - content-length duration

CUSTOM

Will use user defined formatter function.

Transport

The available SockJS transports

Name

Description

WEBSOCKET

rfc 6455

EVENT_SOURCE

Event source

HTML_FILE

HtmlFile.

JSON_P

Slow and old fashioned JSONP polling. This transport will show "busy indicator" (aka: "spinning wheel") when sending data.

XHR

Long-polling using cross domain XHR