Appendix A Expressions Reference 215
HTTP.REQ.HEADER("header_n
ame") “Expression Prefixes for Text in HTTP
Requests and Responses,” on page 67
“Prefixes for HTTP Headers,” on page 116
“Operations for HTTP Headers,” on page 122
HTTP.REQ.FULL_HEADER("hea
der_name") “Prefixes for HTTP Headers,” on page 116
“Operations for HTTP Headers,” on page 122
HTTP.REQ.HOSTNAME “Expression Prefixes for Text in HTTP Requests
and Responses,” on page 67
HTTP.REQ.HOSTNAME.[DOMAIN
| Server] “Expression Prefixes for Text in HTTP Requests
and Responses,” on page 67
“Operations on Text,” on page 86
HTTP.REQ.HOSTNAME.EQ("hos
tname") “Expression Prefixes for Text in HTTP Requests
and Responses,” on page 67
“Booleans in Compound Expressions,” on page 46
“Basic Operations on Expression Prefixes,” on
page 44
HTTP.REQ.HOSTNAME.PORT “Expression Prefixes for Text in HTTP Requests
and Responses,” on page 67
“Compound Operations for Numbers,” on page 48
HTTP.REQ.IS_VALID Returns TRUE if the HTTP request is properly
formed. See “Booleans in Compound Expressions,”
on page 46
HTTP.REQ.METHOD “Expression Prefixes for Text in HTTP Requests
and Responses,” on page 67
“Operations on Text,” on page 86
“Complex Operations on Text,” on page 88
HTTP.REQ.TRACKING Returns the HTTP body tracking mechanism. See
the descriptions of other HTTP.REQ.TRACKING
prefixes in this table.
HTTP.REQ.TRACKING.EQ("tra
cking_mechanism") Returns TRUE or FALSE. See “Booleans in
Compound Expressions,” on page 46
HTTP.REQ.URL Obtains the HTTP URL object from the request and
sets the text mode to URLENCODED by default.
See “Expression Prefixes for Text in HTTP
Requests and Responses,” on page 67
Expression Prefix Notes and Links to Prefix and Applicable Operator
Descriptions