Forum Discussion
Well, let's back up and talk about how this should work.
-
With the HTTP-HTTPS iRule applied to the HTTP VIP, a user might navigate to:
http://myapp.domain.com/ibex1h.ibx?acctnum=9248789&medrec=T01275160&cibex=&pid=&ssn=Server
which hits the HTTP VIP, which issues an immediate redirect to:
https://myapp.domain.com/ibex1h.ibx?acctnum=9248789&medrec=T01275160&cibex=&pid=&ssn=Server
-
That redirect sends the user to the HTTPS VIP, where the application request is served.
The really weird thing is the "Location:%20https://" string in the URI, which is what you would normally find in the header of a redirect. Example:
HTTP/1.0 302 Found
Location: https://something...
...
So I'd suspect something is either intercepting/mangling the HTTP-HTTPS redirect, or this is coming from the application. So let me ask this. From a sequence perspective, when does the client try to make this goofy request, given the following flow:
-
Request to http://myapp.domain.com/ibex1h.ibx?acctnum=9248789&medrec=T01275160&cibex=&pid=&ssn=Server/
-
Redirect to https://myapp.domain.com/ibex1h.ibx?acctnum=9248789&medrec=T01275160&cibex=&pid=&ssn=Server
-
Request to https://myapp.domain.com/ibex1h.ibx?acctnum=9248789&medrec=T01275160&cibex=&pid=&ssn=Server