Disable HTTP 302 Found redirect for B2B use case
Newbie!
Our use case is a B2B REST API and generally no user access via a browser except for testing. We are using TLS 1.2 Mutual Authentication (MA). An HTTP 302 Found including a set of cookies is returned after a successful TLS negotiation. A browser (at least Chrome and Firefox) or Postman deal with the redirect seamlessly, returning part of the cookie in the client request. From a test user experience point of view it all works and the REST API is accessible (the redirect is not visible).
However, when a non-browser (lets for arguments sake say Java) based request is used, the HTTP 302 Found needs to be explictly dealt with, which creates complexity that I am hoping is unnecessary for B2B.
Is the redirect configurable? Can it be disabled? Possibly in an iRule or Access Policy?