Hello,
This iRule is suitable for both - HTTP as well as for HTTPS. The criteria for use is that in case of HTTPS, F5 has to decrypt clientside traffic flow so that the HTTP headers can be inspected. It does not matter if you attach this particular iRule to a HTTP or HTTPS Virtual Server, but in case of HTTPS you must also assign a clientssl profile.
There are no workarounds here, two functions in your iRule require that the clientside traffic flow must be decrypted:
[HTTP::method]
and
[HTTP::request]
. The
[IP::client_addr]
function is the only one which can be used in case of encrypted traffic flow.