Forum Discussion
Frank_30530
Feb 05, 2019Altocumulus
SSL::enable/SSL::disable unexpected behaviour
I have a question about the specific bahaviour of LTM with regard to SSL::enable/SSL::disable.
I have a virtual server with two pools:
One pool has a member that needs TLS communication; The ot...
jaikumar_f5
Feb 06, 2019MVP
Just a thought, I see in your 1st irule you are making SSL disable in the clientside of the connection, Http request. Because when you do not sepcify context side, it will apply to the default connection side. So here it's SSL DISABLE for client SSL alone. But your serverssl is still enabled. Thereby when sent to serverside, serverssl still applies.
when HTTP_REQUEST {
if { } {
select the tls-pool: enable server side SSL
SSL::enable
pool
}
else {
select the http-pool: disable server side SSL
SSL::disable
pool
}
}
If you try the below, it should work too.
when HTTP_REQUEST {
if { } {
select the tls-pool: enable server side SSL
SSL::enable
pool
}
else {
select the http-pool: disable server side SSL
SSL::disable
Not really sure if both context sides can be mentioned in one command :very) SSL::disable clientside serverside
SSL::disable serverside
pool
}
}
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects