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: Tom
Peter:
Here is what I got when using curl on a client.
curl -I http://lb-api:8080/urls?param1=something\¶m2=123
HTTP/1.0 302 Found
Location: https://lb-api:8443/ urls?param1=something\¶m2=123
Server: BigIP
Connection: Keep-Alive
Content-Length: 0
Our engineer who has access to the load balancer is
Peter:
To answer your questions
1. The response header when using 8080 to post, I got:
Status Code: 405 Method Not Allowed
Allow: POST
Cache-Control: private
Content-Language: en
Content-Length: 1045
Content-Type: text/html;charset=utf-8
Date: Mon, 23 Jan 2017 18:48:07
Peter:
Our Load balancer uses a VIP to do the redirect, so when a request coming in as
http://lb-api:8080, it changes it into https://lb-api:8443 and submit to the
api server behind. I could not see any redirect logged into the access log.
However, if I submit a request to the api server directl
Konstantin:
Thank you very much for your reply. To answer your question
1. The api-lb and lb-api was a typo.
2. I was able to reproduce this problem with a single server behind the
load balancer.
Where http://lb-test-api:8080 was set to forward to https://lb-test-api:8443
using vi
Hi, I've been looking for a solution to this question. We have a setup of a
couple api servers running tomcat 7.0.65. For both servers we had http redirect
to https set up so when people access to
http://my-api1:8080, it is automatically redirect to https://my-api1:8443 The
redirect works fine
