Windows Live™ Contacts supports HTTP/1.1 headers from the RFC2616 specification and HTTP/1.1 headers that are specific to Windows Live Contacts.
Windows Live Contacts request headers
No request headers specific to Windows Live Contacts are required.
Windows Live Contacts response headers
No response headers currently exist that are specific to Windows Live Contacts.
RFC2616 standard HTTP request Headers
Windows Live Contacts supports a subset of the headers that are defined in the RFC2616 protocols document that is published by the World Wide Web Consortium:
>http://www.w3.org/protocols/rfc2616/rfc/2616-sec14.html
These headers have no prefix.
Common to all Windows Live Contacts Offers, is the requirement to provide the Authorization header with the Delegated Authentication Token (DAT) taken from the Consent Token returned from the Delegated Authentication Service following Windows Live User consent e.g.
|
Header name
|
Purpose
|
Usage
|
|---|
|
Authorization:
|
Contains the delegated authentication token e.g.
Request.Headers.Add(“Authorization”, “DelegatedToken dt=\”” + DAT + “\””);
|
Mandatory
|
RFC2616 standard HTTP response headers
Windows Live Contacts supports the following response headers that are defined in the RFC2616 protocols. These headers have no prefix.
|
Header name
|
Purpose
|
Usage
|
|---|
|
Last-Modified:
|
Indicates when the entity was last modified in Windows Live Contacts. This header is sent in response to an HTTP/1.1 GET request.
|
Mandatory
|
|
Location:
|
Returns the URI of the newly created entity. This header is sent in response to an HTTP/1.1 POST request.
|
Mandatory
|
Other Resources
Windows Live Contacts API Reference: Address Book Schema
Windows Live Contacts API Reference: Methods
Windows Live Contacts API Reference: Address Books
Windows Live Contacts API Reference: Contacts
Windows Live ID Delegated Authentication SDK for Application Providers