HTTP 302 Required instead of 200 OK

Dear Stanislas, Actually External Logon Page is Another VS on same F5, and based on URI, the iRule sends the request to that VS (host header remains same). Please see the snapshot below. I could not replicate the exact scenario customer has, but I used an internal HTTP Auth Server. Maybe the below snapshot gives a clear idea, where you can see that after the post on /my.policy , F5 gave us a 200 OK and then the next request went to external logon URI which is something like /mfaqasit.....