PDF(4.7 KB) View with Adobe Reader on a variety of devices
Updated:August 12, 2014
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Why am I getting "Bad Request (Request Header Too Long)" error when going through the Cisco Web Security appliance (WSA)?
Cisco Web Security Appliance (WSA) any AsyncOS version
The error "Bad Request (Request Header Too Long)" is seen when the HTTP request header exceeds the "header size limit" set on the destination server.
Normal HTTP requests don't hit this limit. However in certain cases, like the destination server requiring authentication, the HTTP request header may grow, approaching the limit set on the destination server. If the HTTP request header exceeds the header size configured on the destination server, then the server will send "Bad Request (Request Header Too Long)" HTTP response.
When going through the WSA, WSA will add additional headers, such as "Via" header, to the HTTP request. The headers added by WSA are typically optional HTTP headers which comply with HTTP RFC. On rare occasions, the extra header which the proxy adds may cause the header limit to be exceeded on destination server side.
The "Via" header can be disabled on our Web Security Appliance (WSA) from the Web GUI under: