2.1.2 HTTP/HTTPS

When HTTP/HTTPS is used as the transport, the client and server MUST set the HTTP headers that are described in the following table.<4>

Field

Description

SOAPAction

Specifies SOAP action type "urn:schemas-microsoft-com:xml-analysis:Discover" for Discover requests or "urn:schemas-microsoft-com:xml-analysis:Execute" for Execute requests.

X-Transport-Caps-Negotiation-Flags

Used for content type negotiation. The value is a comma-separated list of five values that correspond to NEGO, REQ_SX, REQ_XPRESS, RESP_SX, and RESP_XPRESS.

Content-Type

Specifies the content type of the payload. The value is one of the following:

"text/xml"

"application/sx"

"application/xml+xpress"

"application/sx+xpress"

When HTTP/HTTPS is used as the transport, the client and server can also set the following HTTP headers.

Field

Description

SspropInitAppName

Represents the name of the client application.

X-AS-ActivityID<5>

Specifies a unique identifier that is represented as a GUID and is either passed by an external application via Thread Local Storage or auto-generated.

X-AS-GetSessionToken<6>

Specifies a session token. To request the session token, this field MUST be set to "true".

X-AS-RequestID<7>

Specifies a unique identifier that is represented as a GUID and can be set by a client to track individual commands for a given request.

X-AS-SessionID<8>

Specifies a unique identifier that is retrieved from the response to the BeginSession request and MUST be set in this field. For the initial interaction, this flag is optional.

Content-Encoding<9>

Indicates to the server whether the stream is compressed. When the stream is compressed, the value MUST be set to "deflate".

Authorization<10>

Indicates to the front-end server that the request states the type of authentication and the corresponding token.

  • Last updated on