Version notice:
SERVER_DATA¶
Description¶
For TCP, this event is triggered when new data is
received from the target node after
TCP::collect command has been issued. For
UDP, this event fires on receipt of each segment from
the server. Unlike TCP, no collect is required, and
there is no release command.
Related Information¶
Available Commands:
- clone - Causes the system to clone traffic to the specified pool or pool member regardless of monitor status.
- forward - Sets the connection to forward IP packets.
- IP::idle_timeout - Returns or sets the idle timeout value.
- ip_ttl - Returns the TTL of the latest IP packet received.
- lasthop - Sets the lasthop of an IP connection.
- listen - Sets up a related ephemeral listener to allow an incoming related connection to be established.
- nexthop - Sets the nexthop of an IP connection.
- node - Sends the packet directly to the identified server node.
- peer - Causes the specified iRule commands to be evaluated under the peer’s (opposite) context.
- persist - Causes the system to use the named persistence type to persist the connection.
- session - Utilizes the persistence table to store arbitrary information based on the same keys as persistence.
- TCP::bandwidth - Returns a bandwidth estimate for the peer.
- TCP::client_port - Returns the remote TCP port/service number of the clientside TCP connection.
- TCP::close - Closes the TCP connection.
- TCP::local_port - Returns the local TCP port/service number of a TCP connection.
- TCP::mss - Returns the on-wire Maximum Segment Size (MSS) for a TCP connection.
- TCP::nagle - Enables or disables the Nagle algorithm on the current TCP connection.
- TCP::notify - Causes the USER_REQUEST or USER_RESPONSE event to be raised.
- TCP::offset - Returns the number of bytes currently held in memory via TCP::collect.
- TCP::option - Gets or sets the value of the specified option kind from the TCP header.
- TCP::payload - Returns or replaces TCP data content.
- TCP::release - Releases and flushes collected data. and resumes processing.
- TCP::remote_port - Returns the remote TCP port/service number of a TCP connection.
- TCP::respond - Sends the specified data directly to the peer.
- TCP::rtt - Returns the smoothed round-trip time estimate for a TCP connection.
- TCP::server_port - Returns the remote TCP port/service number of the serverside TCP connection.
- TCP::unused_port - Returns an unused TCP port for the specified IP tuple.
- UDP::client_port - Returns the UDP port/service number of a client system.
- UDP::drop - Drops the current UDP packet without removing the flow from the connection table
- UDP::local_port - Returns the local UDP port/service number.
- UDP::mss - Returns the on-wire Maximum Segment Size (MSS) for a UDP connection.
- UDP::payload - Returns the content or length of the current UDP payload.
- UDP::remote_port - Returns the remote UDP port/service number.
- UDP::respond - Sends data directly to a peer.
- UDP::server_port - Returns the UDP port/service number of a server system.
- UDP::unused_port - Returns an unused UDP port for the specified IP tuple.
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:
- FTP proxy v10 and up - An FTP proxy that simulates FTP proxies found on Bluecoat and Cisco Ironport Proxies
- FTP Session Logging - Log FTP connection and username information
- HTTP Proxy Encapsulator v10/v11 - Allows certain applications to use the HTTP proxy which normally otherwise do not have way to point to the proxy
- iRule_for_passive_ftps_in_ccc_mode - When using ftps with ccc-mode (clear command channel) the ftp-profile on LT…
- LDAP Proxy - An LDAP proxy used send read/write requests to different pools.
- MySQL Proxy - An MySQL proxy used send read/write requests to different pools.
- NAT64 DNS64 - This actually contains 2 iRules. This is a solution that allows client from…
- NAT_iRule - This is a solution that allows client from IPv6 network to communicate to IPv4 network thru BIG-IP.
- RADIUS Load Balancing - An iRule to load balance RADIUS requests.
- Simple traffic shaping - What the rule does is looks at duration of the flow and evaluates the numbe…
- SMTP Start TLS - allows either clear text or TLS encrypted communication with SMTP protocol
- SMTP filter and forward proxy - SMTP filter and forward proxy
- SMTP Proxy - This iRule implements a simple SMTP proxy.
- SMTPStartTLS - This iRule allows either clear text or TLS encrypted communication with the LTM initiating the encryption process if it sees the appropriate “starttls” command in the SMTP communication.
- SOCKS5 SSL Persistence - Much requested 2005 iRule contest winner (thanks Adam!)
- Introduced: BIGIP-9.0.0
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.