cancel
Showing results for 
Search instead for 
Did you mean: 

handle ssl and non ssl on the same virtual server and port

Alexey_Beketov
Nimbostratus
Nimbostratus

Hi!

We have new(ssl) and legacy(non ssl) client applications, both need to connect to the same virtual server and the same 443 port.

Backend server uses plain http.

So we need LTM to accept both ssl / non ssl connections from clients on the same 443 port of the same virtual server and forward them to the backend application.

We tried irules with no success.

Is there any chance we can manage this situation on the LTM side?

 

We have BIG-IP 14.1.2.3 Build 0.0.5 Point Release 3

3 REPLIES 3

Fallout1984
Cirrocumulus
Cirrocumulus

How were the irules configured? Basically, what were they being told to do?

 

If the incoming traffic's port 80 (non-SSL) and it can't be redirected to 443, then a port 80 vserver will be needed. So, you're going to end up with two vservers; one using port 80, one using port 443.

 

 

xuwen
Cirrostratus
Cirrostratus

Local Traffic  ››  Profiles : SSL : Client >>Configuration(Advanced)>>Non-SSL Connections(enable),

use iRules to traffic non ssl to redirect https:

when CLIENTSSL_CLIENTHELLO {

set need_ssl 1

}

when HTTP_REQUEST {

if { ![info exists need_ssl] } {

HTTP::redirect "https://[HTTP::host][HTTP::uri]"

}

}

 

 

 

Its very well in detail explained in this article.

Handling HTTP Requests on an HTTPS Virtual Server