Forum Discussion
rwsalisbury_191
Apr 24, 2015Nimbostratus
Decided not to post the full response received by SoapUI because it is too much detail.
What we have found is that even though the SSL Termination is working fine for HTTP GETs, when a client sends an HTTP POST, BigIP redirects the client to the /my.policy page. And we just want BigIP to pass the POST through to the back-end server just like it does the HTTP GETs. The POSTs happen to be SOAP requests for the back-end server to handle, so the server needs to see the entire original request. And the client is a non-browser application, so there is no smart browser or person to deal with the form that BigIP sends back to the client. This redirect by BigIP did not occur before we implemented SSL Termination.
So here are our current questions:
(1) why does BigIP send a HTTP 301 redirect back to the client when it sees an HTTP POST?
(2) How can we stop it from doing that?
Thank you for any thoughts or ideas you can share.
Richard