302 redirect from apache proxy not coming back on port 80 to VIP

Unanswered Question
Apr 21st, 2008
User Badges:

Client makes request to web server using VIP over port 80. Load balancer forwards request to web server on port 9000.

Web server receives request from client (via LB) on port 9000.

Web server makes request to App server via port 8080.

App Server responds to web server via port 8080 with 302 Redirect to http://dastst-msw-01v.ceg.corp.net:8080/login.jsp?REDIRECTED_FROM=%2F

Web server responds to client via load balancer over port 9000 with 302 Redirect to http://test-dri.bge.com:9000/login.jsp?REDIRECTED_FROM=%2F

Load balancer forwards the 302 Redirect exactly as above over port 80 to the client.

What they don't like is that the load balancer forwards the 302 redirect exactly as it receives it, and doesn't change the port to 80.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Gilles Dufour Tue, 04/22/2008 - 03:29
User Badges:
  • Cisco Employee,

yes, the loadbalancer does not change the content of the http 302 redirect.

The solution would be to catch the client http request that triggers a 302 redirect and generate the redirect from the loadbalancer itself.

Not sure which loadbalancer you are using.

They can all create 302 redirect.

Config would be different depending on the device.


adamkeller Tue, 04/22/2008 - 07:06
User Badges:

It's the CSS running 7.5.

Is there something special on the CSS for the 302?


This Discussion