dual redirect problem..

Hi Jacob --

 

 

Instead of having the app owner change the redirect, you can set LTM's "Redirect Rewrite" option in the http profile applied to the port 443 virtual to "Matching" to re-write redirects with the same hostname to HTTPS rather than HTTP. But I think it might be only part of the problem.

 

 

You say the WebSphere plugin redirects to 3rd party authentication, but the hostname in the redirect is the same as the original requested hostname.

 

 

That means the traffic must be flowing something like this:Port 80:

 

-- client req http://* -> VS:80 -> redirect to https:://* (no problem here if everything is redirected)

 

Port 443:

 

-- client req https://...(main.jsp) -> VS:443 -> forward to pool

 

-- server responds with redirect to https:://.../login.jsp

 

-- client req https://...(login.jsp) -> VS:443 -> redirect to https:://.../main.jsp

 

-- lather, rinse, repeat ad nauseum (the looping behavior you are seeing)Looks like with this iRule in place, and login.jsp page and main.jsp both hosted behind it, the client is never going to hit the login page.

 

 

You mentioned that the WebSphere server is supposed to be redirecting to a 3rd party host for authentication. That would probably solve this situation. If necessary, you can re-write the redirect in the iRule to reference a different location, or if both pages are intended to live behind the iRule, you should add a switch case allowing the login.jsp through without redirecting.

 

 

HTH (As always, post back if you need clarification or if I seem to have it all wrong.)

 

/deb