<p>HTTP Response-splitting can lead to vulnerabilities such as XSS, and cache poisoning.</p>

<p>HTTP Request-splitting can allow an attacker to inject/smuggle an additional HTTP request into a client's outgoing socket connection.

<p>In the context of a servlet container, if the user input includes blank lines,

and if the servlet container does not itself escape the blank lines,

then a remote user can cause the response to turn into two separate responses,

one of which is controlled by the remote user. This is also HTTP Response-splitting.</p>

<p>In the case of code calling Netty API's directly, ensure that the <code>validateHeaders</code> parameter is set to <code>true</code>.</p>

<p>The following example shows the use of the library 'netty' with HTTP request-splitting verification configurations.

The second way will verify the parameters before using them to build the HTTP request.</p>