[env] section

Information in this section can be used to find and fix problems with the site.

This section of the request is auto-populated from the following sources:

HTTP request and response headers are rendered into name/value pairs and inserted into this section of the request. For example, a header item such as accept-encoding=gzip, deflate is rendered as a request name/value pair in the [env] section as the following:
```
HTTP_ACCEPT_ENCODING=gzip, deflate 
```
Some values are inserted by the CX Passive Capture Application at the point of capture. The variable names of some of these values begin with PCA_.
Windows™ pipeline agents, such as Privacy session agent, can be configured to insert data into this section.

Note: The following list contains common examples of values that are inserted into the [env] section. Some of these items are inserted by the PCA for Experience Analytics use. Other items depend on how your web application is configured.

This section also contains many fields that are not indexed and therefore cannot be searched. Many of the non-indexed fields rarely change across all hits of a session. However, since it is possible for them to change on each hit, their values must be captured for each hit.

All variables in this section whose names begin with HTTP_ are standard HTTP request or response variables. For more information, see http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html.

Table 1. [env] section
REQTEXT
Field Name	Use	Source
`CONTENT_TYPE`	The content type for a POST to the server	Client
`CONTENT_LENGTH`	Contents of the HTTP Response Header variable Content-Length	Web Server
`REMOTE_ADDR`	The IP address of the client. If any piece of network equipment in the path between the server and the client terminates and regenerates the IP connection (proxies, reverse proxies, load balancers, and Akamai servers for example) can replace the true client's IP address with its own.	Client
`REMOTE_PORT`	The port over which the client is communicating	Client
`LOCAL_ADDR`	The IP address of the local web server	cxImpact
`LOCAL_PORT`	The port number for the local web server	cxImpact
`SERVER_NAME`	The IP address of the local web server	cxImpact
`SERVER_PORT`	The port number for the local web server	cxImpact
`HTTPS`	When set to `on` page was sent through SSL protocol.	cxImpact
`CONNECTION_ID`	Logical counter that is initiated by the PCA server	PCA
`PCA_NAME`	The name of the PCA server	PCA
`PCA_ADDR`	The IP address for the PCA server	PCA
`PCA_UNAME_RELEASE`	The IP address for the PCA server, as returned from the `uname` command	PCA
`PCA_UNAME_SYSNAME`	The operating system name for the PCA server, as returned from the `uname` command	PCA
`REQUEST_METHOD`	The method of the issued request: `GET` or `POST`	PCA
`URL`	The URI (full page path less machine name and port) requested by the client	Client
`SERVER_PROTOCOL`	HTTP protocol that is used by the server to send responses	Server
`ResponseType`	MIME-Type of the page returned	cxImpact computed
`StatusCode`	The status code from the web server that is returned for the page that is requested by the client	Web Server
`StatusCodeText`	The text equivalent of the `StatusCode` value	Web Server
`RequestHeaderSize`	Request header size in bytes	Web Server
`RequestDataSize`	Request data size in bytes	Web Server
`RequestSize`	The total size of the request: `RequestHeaderSize` + `RequestDataSize`	Web Server
`ResponseHeaderSize`	Response header size in bytes	Web Server
`ResponseDataSize`	Response data size in bytes	Web Server
`ResponseSize`	The total size of the response: `ResponseHeaderSize` + `ResponseDataSize`	Web Server
`REQ_BUFFER_ENCODING`	The encoding method in the request block. Experience Analytics always renders the request block in UTF-8 format.	Web Server
`REQ_BUFFER_ORIG_ENCODING`	Original encoding method (primarily for POST'd data)	Web Server
`RESP_BODY_ENCODING`	The encoding method in the response body. Experience Analytics always renders the response body in UTF-8 format.	Web Server
`ReqCancelled`	Request was canceled by client/server	PCA
`ReqDiscarded`	Request discarded. Note: This feature is not available.	PCA
`StreamingHit`	When set to `true`, the hit is a streaming hit. Note: This feature is not available.	PCA
`StreamingHitType`	When `StreamingHit=true`, this value identifies the type of streaming hit. Note: This feature is not available.	PCA
`HTTP_USER_AGENT`	User agent string that is provided by the visitor's browser	HTTP req/resp header
`HTTP_ACCEPT`	Accepted content encoding types	HTTP req/resp header
`HTTP_ACCEPT_LANGUAGE`	Accepted language	HTTP req/resp header
`HTTP_ACCEPT_ENCODING`	Accepted compression encodings	HTTP req/resp header
`HTTP_ACCEPT_CHARSET`	Accepted character encoding	HTTP req/resp header
`HTTP_KEEP_ALIVE`	If the `HTTP_CONNECTION` value is set to `Keep-Alive`, this value defines the number of seconds that the connection is retained without activity, before it is timed out.	HTTP req/resp header
`HTTP_REFERER`	Referrer of the current hit	HTTP req/resp header
`HTTP_COOKIE`	Contains all cookies that are supplied in the response. These cookies can include: `TLTSID` - session identifier `TLTHID` - hit identifier `TLTUID` - user identifier	HTTP req/resp header
`HTTP_HOST`	Host name	HTTP req/resp header
`HTTP_CONNECTION`	Connection type between the visitor and your web server.	HTTP req/resp header
`CONTENT_LENGTH`	Length in bytes of the response	HTTP req/resp header
`PostRequestBodyEncoding`	This value defines any encoding is applied to requests posted to your web server, as identified by the CX Passive Capture Application. If the binary posts are enabled for capture, this variable is set to `base64`. Otherwise, the value is set to `None`.	PCA

Note: From the HTTP_COOKIE and HTTP_SET_COOKIE fields, it is possible to recognize if your application is replacing its session variable in the middle of a visitor session, which can be an indicator of the visitor experience in which the contents of their shopping cart have disappeared.

Join the community

Academy

Request view

Related articles

Join the community

Academy