For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

cdougall_14195's avatar
cdougall_14195
Icon for Cirrus rankCirrus
Mar 25, 2015

You're pretty much stuck with using something unique unless you're willing to add the HTTP and SSL profiles.

The easy solution would be to have a dedicated pool to service the sorry pages. You can't do redirects or mess with the unencrypted headers unless you apply those other profiles..

when CLIENT_ACCEPTED {
  if { [active_members [LB::server pool]] == 0} {
    if { [TCP::local_port clientside] eq "443" } {
        pool sorry_https_pool
    } else {
        pool sorry_http_pool
    }
  }
}

Probably worth noting that this since you're not terminating SSL, you would need to have one pool for HTTP and one for HTTPS.

Martin_Vlasko's avatar
Martin_Vlasko
Icon for Altocumulus rankAltocumulus
Mar 26, 2015
My virtual server listens only to port 443, so I assume I don't need to care about HTTP. But the suggestion below from THi looks promising, I will give it a try.