ltm rule command HTTP release

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



HTTP::release
       Releases the data collected via HTTP::collect.

SYNOPSIS
       HTTP::release

DESCRIPTION
       Releases the data collected via HTTP::collect. Unless a subsequent
       HTTP::collect command was issued, there is no need to use the
       HTTP::release command inside of the HTTP_REQUEST_DATA and
       HTTP_RESPONSE_DATA events, since (in these cases) the data is
       implicitly released.  It is important to note that these semantics are
       different than those of the TCP::collect and TCP::release commands.
       With TCP::collect, the event for processing the data (CLIENT_DATA) will
       fire without TCP::release being called, whereas with HTTP::collect, the
       event (HTTP_REQUEST_DATA or HTTP_RESPONSE_DATA) will not fire without
       HTTP::release being called (at least implicitly).

       Syntax

       HTTP::release

	    * Releases the collected data.

RETURN VALUE
VALID DURING
       ANY_EVENT

EXAMPLES
	when CLIENT_ACCEPTED {
	    set tmm_auth_ldap_sid [AUTH::start pam default_ldap]
	}
	when HTTP_REQUEST {
	    AUTH::username_credential $tmm_auth_ldap_sid [HTTP::username]
	    AUTH::password_credential $tmm_auth_ldap_sid [HTTP::password]
	    AUTH::authenticate $tmm_auth_ldap_sid
	    HTTP::collect
	}
	when AUTH_SUCCESS {
	       if {$tmm_auth_ldap_sid eq [AUTH::last_event_session_id]} {
		       HTTP::release
	       }
	}
	when AUTH_FAILURE {
	       if {$tmm_auth_ldap_sid eq [AUTH::last_event_session_id]} {
		       HTTP::respond 401
	       }
	}
	when AUTH_WANTCREDENTIAL {
	       if {$tmm_auth_ldap_sid eq [AUTH::last_event_session_id]} {
		       HTTP::respond 401
	       }
	}
	when AUTH_ERROR {
	       if {$tmm_auth_ldap_sid eq [AUTH::last_event_session_id]} {
		       HTTP::respond 401
	       }
	}

HINTS
SEE ALSO
CHANGE LOG
       @BIGIP-9.0.0 --First introduced the command.



BIG-IP				  2017-01-31			      iRule(1)