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: