ltm rule command PROFILE exists

iRule(1)		      BIG-IP TMSH Manual		      iRule(1)



PROFILE::exists
       Determine if a profile is configured on a virtual server.

SYNOPSIS
       PROFILE::exists TYPE (NAME)?

       PROFILE::exists persist MODE (NAME)?

DESCRIPTION
       Determine if a profile is configured on a virtual server.

       Note that the results of the PROFILE::exists "profile type" command is
       specific to the context of the event. For example, with a client SSL
       profile associated with the virtual server, PROFILE::exists clientssl
       will return 1 in clientside events and 0 in serverside events.
       Likewise, PROFILE::exists serverssl will return 0 in clientside events
       and 1 in serverside events.

RETURN VALUE
       Returns 1 if the profile is configured on the current virtual server.
       Returns 0 if the profile is not configured on the current virtual
       server.

VALID DURING
       ANY_EVENT

EXAMPLES
	when CLIENT_ACCEPTED {
	   if { [PROFILE::exists clientssl] == 1} {
	      log local0. "client SSL profile enabled on virtual server"
	   }
	}
	when SERVER_CONNECTED {
	   if { [PROFILE::exists serverssl] == 1} {
	      log local0. "server SSL profile enabled on virtual server"
	   }
	}

HINTS
SEE ALSO
       HTTP and HTTPS on a single virtual server
       
       - iRule to support a virtual server on port 0 and a client SSL profile.
       and a...  ProxyPass (for LTM v9 only)
        - iRule to
       replace the functionality of Apache Webserver ProxyPass and
       ProxyPassReverse functions ProxyPass v10/v11
        - iRule (for
       LTM v10/v11) to replace the functionality of Apache Webserver ProxyPass
       and ProxyPassReverse functions allowing for a different server and
       client view of your web application(s).

CHANGE LOG
       @BIGIP-9.0.3 --First introduced the command.



BIG-IP				  2019-05-10			      iRule(1)