2.2.1.1.2 Request Headers

The HTTP/1.1 protocol ([RFC2616]) defines several headers that can be sent from the client to the server on an HTTP POST request. The headers follow the request line in the HTTP portion of a request. The following headers are used in ActiveSync synchronization protocol requests. Note that requests are UTF-8 encoded.

Header

Required

Notes

Accept-Language

No. 

For details, see section 2.2.1.1.2.1.

Authorization

Yes, if using basic or OAuth authentication.

For details, see section 2.2.1.1.2.2.

Content-Type

Depends on the command.

Specifies that the media type of the request body is WBXML. Other types of content, such as [RFC2822], can also be specified, depending on the command. For more details, see section 2.2.1.1.2.3.

Cookie

Depends on the contents of previous server responses and the protocol version in use.

Contains one or more cookies that the client previously received from the server in a Set-Cookie header. For more details, see section 2.2.1.1.2.4.

MS-ASAcceptMultiPart

No

Specifies that the client wants items returned in multipart format. For more details, see section 2.2.1.1.2.5.

MS-ASProtocolVersion

No if using a base64 encoded query value; yes if using a plain text query value.

Specifies the version of the ActiveSync protocol that the client supports. For more details, see section 2.2.1.1.2.6.

User-Agent

No

Contains information about the client sending the request. For more details, see section 2.2.1.1.2.7.

X-MS-PolicyKey

Depends on the command.

Specifies the policy key assigned by the server to the client. For more details, see section 2.2.1.1.2.8.

Show: