QuestionQ61

Identify and Resolve LTM Device Issues

An LTM Specialist has a OneConnect profile and an HTTP profile configured on a virtual server to load-balance an HTTP application.

The following HTTP headers appear in a network trace when a client connects to the virtual server:

Clientside:

GET / HTTP/1.1 -  
  
Host: 192.168.136.100 -  
  
User-Agent: Mozilla/5.0 -  
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8  
  
Accept-EncodinG. gzip, deflate -  
  
Connection: keep-alive -  

Serverside:

HTTP/1.1 200 OK -  
  
DatE. 5 Jun 1989 17:06:55 GMT -  
Server: Apache/2.2.14 (Ubuntu)  
  
Vary: Accept-Encoding -  
  
Content-EncodinG. gzip -  
  
Content-LengtH. 3729 -  
  
X-Cnection: close -  
  
Content-TypE. text/html -  

The LTM Specialist observes that the OneConnect feature is operating incorrectly.

Why is OneConnect operating incorrectly?

  • A Client must support HTTP/1.0.
  • B Client must support HTTP keep-alive.
  • C Server must support HTTP/0.9.
  • D Server must support HTTP keep-alive.
Explanation

OneConnect pools and reuses idle server-side connections. HTTP traffic is eligible for OneConnect only when the back-end web server supports HTTP Keep-Alive connections; otherwise, the server-side connection cannot remain open for reuse.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!