Forum Discussion
This solution SOL2167: Constructing HTTP requests for use with the HTTP or HTTPS application health monitor covers the functionality.
This is a portion of the solution: 10.2.x and 11.x
Each instance of \r is translated to a CR character (0x0d).
Each instance of \n is translated to a LF character (0x0a).
No CR/LF sequences are appended to the end of the Send String unless Basic Authentication is enabled.
When Basic Authentication or NTLM / NTLMv2 Authentication (version 11.1 and later) is enabled by configuring a User Name and Password in the monitor definition, the system inserts the Authorization header and a terminating double CR/LF sequence (0x0d 0x0a 0x0d 0x0a) after the last character in the Send String.
9.4.x, 9.6.x, 10.0.x, 10.1.x
Each instance of \r is translated to a CR character (0x0d).
Each instance of \n is translated to a LF character (0x0a).
A double CR/LF sequence (0x0d 0x0a 0x0d 0x0a) is appended to the end of the Send String.
9.2.x and 9.3.x
Each instance of \r is translated to a CR character (0x0d).
Each instance of \n is translated to a LF character (0x0a).
A single CR/LF sequence (0x0d 0x0a) is appended to the end of the Send String.
9.0.x and 9.1.x
Each instance of \n is translated to a CR+LF character sequence (0x0d 0x0a).
A single CR/LF sequence (0x0d 0x0a) is appended to the end of the Send String.