Does the ProxySG support non standard HTTP request headers?
Last Updated May 13, 2017
Some custom HTTP applications (that are used within an organization for internal processes) do not comply with the RFC completely. For example, if the HTTP request header contains a space before the colon in the user agent "User-Agent :custom_agent" the ProxySG will return a 400 bad request error to the client.
Is there a way we can customize the rules on the ProxySG so that it accepts non-RFC standard headers? Is there a supported non-standard HTTP request header list?
Yes, the ProxySG supports the non-standard HTTP request headers in the following cases:
Supports all unknown request methods
Supports case-insensitive HTTP version
Ignores up to 10 blank lines at the beginning of the request
Ignores up to 2 null characters at the beginning of the request
Ignores a null character at the end of request line or any request header
Allows extra blank lines in chunk encoding
Allows one trailing slash at the end of host:port syntax in the CONNECT method
When (config) http tolerant-request-parsing is enabled
Treats white space followed by LF as end of headers
Allows white space between header name and colon
Imported Document ID: 000009123
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe