serverside

Description¶

Causes the specified iRule command or commands to be evaluated under the server-side context. This command has no effect if the iRule is already being evaluated under the server-side context.

Syntax¶

serverside
serverside { <iRule command> }

serverside¶

Returns 1 if the current event is in the serverside context or 0 if not.

serverside { <iRule command> }¶

Causes the specified iRule command or commands to be evaluated under the server-side context.

Examples¶

when CLIENT_ACCEPTED {

   # Check if the server (pool member) IP address is 10.1.1.80
   # [serverside {IP::remote_addr}] is equivalent to [IP::server_addr]
   if { [IP::addr [serverside {IP::remote_addr}] equals 10.1.1.80] } {

      # Do something like drop the packets in this example
      discard
   }
}

Related Information¶

Valid Events:

CLIENT_ACCEPTED

Warning

The links to the sample code below are remnants of the old DevCentral wiki and will result in a 404 error. For best results, please copy the link text and search the codeshare directly on DevCentral.

Sample Code:

SIP topology hiding and forward proxy - SIP calls from inside to outside are forward with topology hiding.

Introduced: BIGIP-9.0.0

Changelog¶

LTM 11.5.2, 11.5.3, 11.6.0, 12.0.0

A runtime check is added: if the server side connection does not exist, this command aborts execution and returns a TCL error. One common problem is such script: “serverside {SSL::disable}” when there is no server side connection, it needs to be updated to “SSL::disable serverside”.

The BIG-IP API Reference documentation contains community-contributed content. F5 does not monitor or control community code contributions. We make no guarantees or warranties regarding the available code, and it may contain errors, defects, bugs, inaccuracies, or security vulnerabilities. Your access to and use of any code available in the BIG-IP API reference guides is solely at your own risk.