QuestionQ161

Identify and Resolve Application Issues

An LTM Specialist configured a virtual server to load-balance a custom application. The application functions when tested from inside the firewall but fails when tested externally. The pool-member address is 192.168.200.10:80. A capture from an external client shows:

GET /index.jsp HTTP/1.1 -  
  
Host: 207.206.201.100 -  
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20100101 Firefox/15.0.1  
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8  
  
Connection: keep-alive -  
  
HTTP/1.1 302 Found -  
DatE. Wed, 17 Oct 2012 23:09:55 GMT  
Server: Apache/2.2.15 (CentOS)  
Location: http://192.168.200.10/user/home.jsp  
  
Content-LengtH. 304 -  
  
Connection: close -  

What is the solution to this issue?

  • A Assign a SNAT pool to the virtual server.
  • B Add a Web Acceleration Profile to the virtual server.
  • C Configure redirect rewrite option in the HTTP profile.
  • D Configure a content filter on the backend web server.
Explanation

The backend server redirects the client to a private pool-member IP address in the HTTP Location header. An externally connected client cannot route to that address. BIG-IP HTTP-profile redirect rewriting changes redirect URLs in the Location header; its Nodes option hides the node IP address by replacing it with the virtual-server address and rewrites the port as needed.

Learn more

Community Discussion

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