The LTM Specialist is writing a custom HTTP monitor for a web application and has viewed the content by
accessing the site directly via their browser. The monitor continually fails. The monitor configuration is:
ltm monitor http /Common/exampleComMonitor {
defaults-from /Common/http
destination *:*
interval 5
recv “Recent Searches”
send “GET /app/feed/current\\?uid=20145 HTTP/1.1\\\\r\\\\nHost:
www.example.com\\\\r\\\\nAccept-EncodinG. gzip, deflate\\\\r\\\\nConnection: close\\\\r\\\\n\\\\r\\\\n” time-until-up 0
timeout 16
}
A trace shows the following request and response:
Request:
GET /app/feed/current?uid=20145 HTTP/1.1
Host www.example.com
Accept-Encoding gzip, deflate
Connection: close
Response:
HTTP/1.1 302 Moved Temporarily
Date Wed, 17 Oct 2012 18:45:52 GMT
Server Apache
Location https://example.com/login.jsp
Content-Encoding gzip
Content-Type text/html;charset=UTF-8
Set-CookiE. JSESSIONID=261EFFBDA8EC3036FBCC22D991AC6835; Path=/app/feed/current?
uid=20145
What is the problem?

A.
The request does NOT include a User-Agent header.

B.
The HTTP monitor does NOT support monitoring jsp pages.

C.
The request does NOT include any cookies and the application is expecting a session cookie.

D.
The request includes an Accept-Encoding so the server is responding with a gzipped result and LTM
monitors CANNOT handle gzipped responses.