HTTP codec is a service that uses TCP-Lite as an underlying transport. This transport provides a reduction in the over-the-air (OTA) byte count by removing or byte-encoding header fields in a HyperText Transport Protocol (HTTP) data stream.
On the SafeLinx Client, an HTTP codec removes or encodes HTTP request headers and transmits the HTTP data stream. Then, an HTTP codec reconstitutes the request headers at the SafeLinx Server before passing the traffic to target web servers. Then, the SafeLinx Server removes or encodes the HTTP response headers before passing the traffic to the Mobility Client.
- The TCP-Lite transport property values that are used
the Host token specified is processed in request headers.
Choose from these options in which the HTTP codec:
- Removes the header if it exactly matches what is specified and encodes headers that do not match
- Removes the header if it exactly matches what is specified and returns an HTTP status code 403 to the requester for headers that do not match
- Removes the Host token in all request headers sent from the Mobility Client. Then, replaces it with a different Host token at the Connection Manager before passing the request on
- How the uniform
resource identifier (URI) is processed in request
headers. Choose from these options in which the HTTP codec:
- Removes the URI if it exactly matches what is specified and passes URIs that do not match
- Removes only the portion of the URI which matches the value of the URI field specified. When the request header is received at the SafeLinx Server, the HTTP codec adds the prefix value onto the beginning of the URI field before passing the request on.
- Which HTTP header tokens are encoded and transmitted. Tokens that are not selected are removed from the header.
- Whether tokens in the header which are not listed are transmitted or not.