- Jul 01 Mon 2013 19:26
- Sep 19 Wed 2012 18:30
- Sep 19 Wed 2012 18:26
- Jun 19 Tue 2012 13:02
- Feb 08 Wed 2012 15:52
- Dec 14 Wed 2011 19:08
- Aug 09 Tue 2011 20:46
Windows Mobile software for Pocket PC Edition and Smartphone processes the push headers shown in the following table.
|Content-Type||A required header that is implemented as defined in HTTP/1.1.|
|Content-Location||A header that is implemented as defined in HTTP/1.1.|
|Push-Flag||A bit mask flag that indicates if the initiator Uniform Resource Identifier (URI) is authenticated and the content is trusted. This flag is implemented as defined in the WAP-189-PushOTA Version 17-Feb-2000 specification.|
|X-WAP-Application-ID||A generic header that provides an application identifier (ID). This header is implemented as defined in the WAP-189-PushOTA Version 17-Feb-2000 specification.|
|X-WAP-Content-URI||A generic header that is used in caching to identify the URI of the HTTP request.|
|X-WAP-Initiator-URI||A generic header that identifies the WAP push initiator.|
|X-MS-DESC||A custom header designed to provide a brief description of the purpose of the push message. This description is displayed to the user if the user is presented with a dialog box to enter a personal identification number (PIN). This dialog box would appear during the authentication process for the message.|
The following is a WAP push message that can be processed by the Push Router. In the header, the content type is identified as a WAP connectivity document.