|Value entered in the client’s authentication dialog. This variable is available only if Basic authentication is used.
|Contains the authentication method that the server uses to validate users when they attempt to access a protected script.
|For requests which have attached information, such as HTTP POST and PUT, this is the content type of the data.
|Revision of the CGI specification to which this server complies. Format: CGI/revision
|Value of the Accept request header that contains a list of accepted formats (MIME types). For example: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel. The values of the fields for the HTTP_ACCEPT variable are concatenated, and separated by a comma (,).
|Comma-delimited list of the character encodings that the client accepts.
|Contains a string describing the language to use for displaying content (such as en-us).
|Contains the Base-64 encoded username, password, scheme and realm sent by the client.
|Holds the contents of the client’s cookie(s).
|Holds a string that contains the URL of the page that referred the request to the current page using an HTML <A> tag. Note that the URL is the one that the user typed into the browser address bar, which may not include the name of a default document. If the page is redirected, HTTP_REFERER is empty.
|SOAPAction HTTP request header field can be used to indicate the intent of the SOAP HTTP request. The value is a URI identifying the intent. SOAP places no restrictions on the format or specificity of the URI or that it is resolvable. An HTTP client MUST use this header field when issuing a SOAP HTTP Request.
|Browser the client is using to send the request. General format: software/version library/version.
|Set to either On or Off (using word, not numerical value). Set to on if the script is being called through a secure server (that is, using SSL/TLS).
|Translated version of PATH_INFO, in which any virtual-to-physical mapping is applied to the path.
|IP address of the remote host making the request.
|Hostname making the request. If the server does not have this information, it should set REMOTE_ADDR and leave this parameter unset.
|If the HTTP server supports RFC 931 identification, then this variable is set to the remote username retrieved from the server.
|Name of the user as it is derived from the authorization header sent by the client
|Method with which the request was made. For HTTP, this is GET, HEAD, POST, and so on.
|The server's hostname, DNS alias, or IP address as it would appear in self-referencing URLs.
|Port number to which the request was sent. For example: 80
|Set to either 0 or 1. If the request is being handled on the web server’s secure port, then it is set to 1. Otherwise, it is set to 0.
|Name and revision of the information protocol that the request came in with. Format: protocol/revision
|Name and version of the web server software responding to the request. Format: name/version.