http post header modification method

What Persistence are you using?

 

 

HTTP Cookie Insert: Specifies that the system inserts server information, in the form of a cookie, into the header of the server response. This is the default setting.

Hi John,

 

 

Can you clarify what the issue is?

 

 

Is it that the web app doesn't recognize the HTTP host header in requests because the request is being made to the virtual server IP address? If so, does the failure still occur if the client accesses the VS using a hostname? What hostname(s) does the application expect? Is the required value specific to the individual

 

 

Or is the issue that the servers are sending a redirect with the wrong IP address or hostname in the Location header?

 

 

Aaron

Cookie persistance.

 

 

Looking into this further using an a known good vip and pool now I am puzzled as what the problem is. Switching pools and sending a soap envelope through this vip work fine. Switching pools back to the problem pool sending a different soap envelope intended for these members ends up in a redirect.

 

 

Sending a soap envelop to the F5 vip the endpoint (pool member)will respond with a 302 from the endpoint (pool member)that the address has moved to the to the VIP.

 

 

We are using SOAPUI for test and sending the same envelope directly to the server it works fine which makes me think the F5 configuration, but the F5 is indeed sending the request to the pool member. I guess the question is when using soapui and sending the request to the server it works, but sending to the VIP the endpoint redirects back to the VIP (whats the difference). I been still looking at traces all day but don't see what is tripping this up.

 

 

Thanks again for the help..