Peter: Checked F5 and found that it was the proper behavior of F5 in this http to https redirect. There is a way to use iRule to change that.
Thank you very much! Bin -----Original Message----- From: Kreuser, Peter [mailto:pkreu...@airplus.com] Sent: Wednesday, January 25, 2017 1:22 AM To: Tomcat Users List <users@tomcat.apache.org> Subject: AW: https redirect failed for POST request when behind a load balancer Bin, So it is working as designed in the RFC... https://urldefense.proofpoint.com/v2/url?u=https-3A__en.wikipedia.org_wiki_HTTP-5F302&d=DwIGaQ&c=uilaK90D4TOVoH58JNXRgQ&r=T34XNMuHs99f3YkStEdBgUp9XTcpTRir8U9GVk2H5hQ&m=Cd24gJffDyonEJHgpKqwRRHfhBVcnuh3ZXbrUn1wq6w&s=O-RpRIWcNXyjocbL9uVgxk9VkouVffRloYNsr1Jq7xM&e= -> 302 leads to a resend with GET. If your client would speak HTTP/1.1, a 307 response code could be interpreted as preserving the request type as originally sent. It may be feasible to send this RC in a BigIP iRule for this specific URL. But it is still depending on the client implementation. And I have not seen this in the wild. Now: how does the client get to the POST with http? If your app runs in a regular browser and uses relative URLs, upgrade the first request to https (probably a GET), then after that all links, forms will be on https. Best regards Peter
