iRule - HTTP Response (Trigger)?

For some reason, F5 removed the 'match across' functionality for cookie persistence. I think there is a CR requesting to have it added back. You might request to have your case attached to the request if it hasn't been already.

If you're not using ASM or WebAcc, you could create a single virtual server on port 0 (any) pointing to a pool of web servers also on port 0. You'd need to add a client SSL profile on the virtual server and then use "SSL::disable" in an iRule to disable decryption for requests to an HTTP port. You could then use a cookie insert persistence profile to persist requests irrespective of the port.

I think this would be the simplest method.

Here's an example rule:

when CLIENT_ACCEPTED {
   switch [TCP::local_port] {
      80 {
          need to disable client SSL for HTTP requests
         SSL::disable
      }
      443 {
          do nothing, request will be decrypted and sent to pool
      }
      default {
          drop or reject the request as it's not an allowed port
         reject
      }
   }
}

Aaron