Metabase App

Cut downtime and deliver reliable applications and services at high velocity with a DevOps automation platform. Start with our 14-days trial. MetaBank’s mobile banking is your bank when you need it. Review your balance and transaction history. Transfer funds between your MetaBank accounts. Schedule online bill payments. Send and receive funds to and from your friends. Locate ATMs and MetaBank branch locations. Download the MetaBank smartphone app for fast.

-->

IIS Server Variables provide information about the server, the connection withthe client, and the current request on the connection. Additionally, inboundURL rewrite rules can be used to set custom server variables.

Note

Reviews for knives out. Not all server variables listed in this document are available in versions of IIS prior to IIS 8.5.

Server VariableDescription
ALL_HTTPAll HTTP headers sent by the client. The headers are prefixed by with HTTP_ and capitalized.
For example, HTTP_ACCEPT_ENCODING:gzip, deflate, br
ALL_RAWAll HTTP headers sent by the client in raw form.
For example, Accept-Encoding: gzip, deflate, br
APPL_MD_PATHThe metabase path of the application.
APPL_PHYSICAL_PATHThe physical path of the application.
APP_POOL_CONFIGThe physical path of the temporary IIS application pool configuration.
APP_POOL_IDThe name of the application pool that is running the IIS worker process handling the request.
AUTH_PASSWORDThe password provided by the client to authenticate using Basic Authentication.
AUTH_TYPEThe authentication method that the server uses to validate users.
It does not mean that the user was authenticated if AUTH_TYPE contains a value and the authentication scheme is not Basic or integrated Windows authentication. The server allows authentication schemes it does not natively support because an ISAPI filter may be able to handle that particular scheme.
AUTH_USERThe name of the user as it is derived from the authorization header sent by the client, before the user name is mapped to a Windows account. This variable is no different from REMOTE_USER. If you have an authentication filter installed on your Web server that maps incoming users to accounts, use LOGON_USER to view the mapped user name.
CACHE_URLFor use in ISAPI applications only. Returns the unambiguous name for the current URL. It is necessary to use the Unicode version of this variable in conjunction with the kernel mode cache invalidation function to evict entries placed in the cache by HSE_REQ_VECTOR_SEND.
CERT_COOKIEUnique ID for the client certificate, returned as a string. This can be used as a signature for the whole client certificate.
CERT_FLAGSbit0 is set to 1 if the client certificate is present.
bit0 is set to 1 if the certification authority of the client certificate is invalid (that is, it is not in the list of recognized certification authorities on the server).
If bit 1 of CERT_FLAGS is set to 1, indicating that the certificate is invalid, IIS version 4.0 and later will reject the certificate. Earlier versions of IIS will not reject the certificate.
CERT_ISSUERThe issuer field of the client certificate.
CERT_KEYSIZEThe number of bits in the SSL/TLS connection key size.
CERT_SECRETKEYSIZEThe number of bits in the SSL/TLS server private key.
CERT_SERIALNUMBERSerial number of the client certificate.
CERT_SERVER_ISSUERThe issuer field of the server certificate.
CERT_SERVER_SUBJECTThe subject field of the server certificate.
CERT_SUBJECTThe subject field of the client certificate.
CONTENT_LENGTHThe length of the request body.
CONTENT_TYPEThe MIME type of the request body. Used with queries that have attached information, such as GET, POST, and PUT.
CRYPT_CIPHER_ALG_IDThe cryptographic cipher algorithm used to establish the connection. The hex value of the algorithm is established in the ALG_ID data type.
For example, 256-bit AES(CALG_AES_256) will be 6610.
CRYPT_HASH_ALG_IDThe hashing algorithm used for generating Message Authentication Codes (MACs). The hex value of the algorithm is established in the ALG_ID data type.
For example, MD5(CALG_MD5) will be 8003.
CRYPT_KEYEXCHANGE_ALG_IDThe key-exchange algorithm used to establish the connection. The hex value of the algorithm is established in the ALG_ID data type.
For example, Elliptic curve Diffie-Hellman key exchange algorithm(CALG_ECDH) will be aa05.
CRYPT_PROTOCOLThe cryptographic protocol used to establish the connection. The hex value of the protocol is established in the SecPkgContext_ConnectionInfo structure.
For example, TLS 1.2 will be 400.
DOCUMENT_ROOTThe physical path of the directory the IIS Website.
FORWARDED_URLThe forwarded URL.
GATEWAY_INTERFACEThe revision of the CGI specification used by the server. The format is CGI/revision.
HTTPSReturns ON if the request came in through a secure channel (for example, SSL); or it returns OFF, if the request is for an insecure channel.
HTTPS_KEYSIZENumber of bits in the SSL/TLS connection key size.
HTTPS_SECRETKEYSIZENumber of bits in the server certificate private key.
HTTPS_SERVER_ISSUERIssuer field of the server certificate.
HTTPS_SERVER_SUBJECTSubject field of the server certificate.
HTTP_METHODThe method used to make the request.
HTTP_URLThe raw encoded URL.
For example, /vdir/default.aspx?querystring
HTTP_VERSIONThe name and version of the request protocol (the raw form of SERVER_PROTOCOL).
INSTANCE_IDThe IIS site ID.
INSTANCE_META_PATHThe metabase path for the instance of IIS that responds to the request.
INSTANCE_NAMEThe IIS site name.
LOCAL_ADDRThe server address on which the request came in. This is important on computers where there can be multiple IP addresses bound to the computer, and you want to find out which address the request used.
LOGON_USERThe Windows account that the user is impersonating while connected to your Web server. Use REMOTE_USER, UNMAPPED_REMOTE_USER, or AUTH_USER to view the raw user name that is contained in the request header. The only time LOGON_USER holds a different value than these other variables is if you have an authentication filter installed.
MANAGED_PIPELINE_MODEThe managed pipeline mode of the application pool that is running the IIS worker process handling the request.
PATH_INFOPath information, as given by the client, for example, /vdir/myisapi.dll/zip. If this information comes from a URL, it is decoded by the server before it is passed to the CGI script or ISAPI filter.
If the AllowPathInfoForScriptMappings metabase property is set to true (to support exclusive CGI functionality), PATH_INFO will only contain /zip and ISAPI applications such as ASP will break.
PATH_TRANSLATEDThe physical path that maps to the virtual path in PATH_INFO, for example, c:inetpubwwwrootvdirmyisapi.dll. This variable is used by IIS during the processing of ISAPI applications.
If the AllowPathInfoForScriptMappings metabase property is set to true (to support exclusive CGI functionality), PATH_INFO will only contain /zip and ISAPI applications such as ASP will break.
QUERY_STRINGQuery information stored in the string following the question mark (?) in the HTTP request.
REMOTE_ADDRThe IP address of the remote host that is making the request.
REMOTE_HOSTThe name of the host that is making the request. If the server does not have this information, it will set REMOTE_ADDR and leave this empty.
REMOTE_PORTThe client port number of the TCP connection.
REMOTE_USERThe name of the user as it is derived from the authorization header sent by the client, before the user name is mapped to a Windows account. If you have an authentication filter installed on your Web server that maps incoming users to accounts, use LOGON_USER to view the mapped user name.
REQUEST_FILENAMEThe physical path for the current request.
REQUEST_FLAGSThe Flags of HTTP_REQUEST.
For example, the HTTP_REQUEST_FLAG_HTTP2 flag will be set for HTTP/2 requests.
REQUEST_METHODThe method used to make the request.
REQUEST_URIThe path-absolute part of the URI.
For example https://contoso.com:8042/over/there?name=ferret would return /over/there
SCRIPT_FILENAMEThe physical path of the current request.
SCRIPT_NAMEA virtual path to the script being executed.
SCRIPT_TRANSLATEDThe extended-length path to the requested file (prefixed with ?).
SERVER_ADDRThe IP address that the site is bound to.
SERVER_NAMEThe server's host name, DNS alias, or IP address as it would appear in self-referencing URLs.
SERVER_PORTThe server port number to which the request was sent.
SERVER_PORT_SECUREA string that contains either 0 or 1. If the request is being handled on the secure port, then this is 1. Otherwise, it is 0.
SERVER_PROTOCOLThe name and revision of the request information protocol. The format is protocol/revision. (The canonicalized form of HTTP_VERSION.)
SERVER_SOFTWAREThe name and version of the server software that answers the request and runs the gateway. The format is name/version.
UNENCODED_URLThe raw unencoded URL.
UNMAPPED_REMOTE_USERThe name of the user as it is derived from the authorization header sent by the client, before the user name is mapped to a Windows account (same as REMOTE_USER). If you have an authentication filter installed on your Web server that maps incoming users to accounts, use LOGON_USER to view the mapped user name.
URLThe base portion of the URL without any querystring information.
Skip to end of metadataGo to start of metadata

Welcome to the Ed-Fi Tech Docs site! This site has information about Ed-Fi Standards, the Ed-Fi Technology Suite, as well as links to resources for the Ed-Fi community. Know what you're looking for? See the Quick Links below.

Start Here

General resources to get started with everything the Ed-Fi Alliance has to offer.

Products & Technology

Links to Ed-Fi product catalog information and product documentation.

Ed-Fi Standards

General resources and links to Ed-Fi data standards and documentation.

What's New

The latest Ed-Fi product updates and contributions from the community on the Ed-Fi Exchange.

Code & Developer Resources

Information, source code, and technical material for developers and technologists.

Community & Governance

Resources and links to get connected with the Ed-Fi community.

Metabase Embedding

Recent Releases

  • Ed-Fi Data Standard v3.3 (early access)

Starter Kits

Community Resources

  • EE (login required)

Communities of Practice

Support

Code Repositories

  • Ed-Fi Open Source Code (GitHub)
  • Ed-Fi Exchange Open Source Code (GitHub)

Developer Resources

Metabase
  • Ed-Fi Slack Channel (Slack)
  • Ed-Fi Tracker (Jira)
  • Data Mapping Tool (MappingEDU)

Product Documentation

  • ODS / API v5.2 (latest)
  • Dashboards v3.0 (latest)

Metabase Application Database

All Versions & Compatibility

Metabase App Download


Metabase Application

Standards

Metabase App Engine

  • Ed-Fi Data Handbook v3.1 (current)
  • Ed-Fi Data Handbook v3.2.0-c (latest)
  • Ed-Fi Data Standard v3.1 (current)
  • Ed-Fi Data Standard v3.2.0-c (latest)
  • Ed-Fi Data Standard v3.3 (early access)

Governance & Work Groups

  • Governance Home (login required)
Comments are closed.