The following is an example of a response header.
POST http://www.mydomain.com/WebAuth/webauth-handler.aspx HTTP/1.1
…
action=login&
appctx=welcomepage&
stoken=MA12BCF0012BAM567890MABD123456ABCDEF12345667890
The POST body contains three parameters, described in the following table.
|
Parameter
|
Description
|
|---|
|
action
|
The action that the user is doing. The list of possible values is as follows:
-
login—The user has completed a successful sign-in to your site. This value appears in the HTTP POST response only.
-
clearcookie—The Windows Live ID sign-out page is calling your site to clear user cookies. This value appears in the HTTP GET response.
-
logout—The user has completed a successful sign out from Windows Live. This value appears in the HTTP GET response.
Note:
The clearcookie action is always called before logout.
For more information about working with the action parameter, see Handling the Response from the Service.
|
|
appctx
|
The context parameter you passed when constructing the src attribute for the IFRAME displaying the sign-in link. You can use this parameter to keep track of what page the user was on or other user-state information. For more information about the context parameter, see Displaying the Sign-in Link.
|
|
stoken
|
The encrypted data that contains the unique ID, application ID, timestamp, signature, and flags for the user. For more information about the token, see Token Format.
|

See Also