1. SCOPE
2. DOCUMENT STATUS
2.1 COPYRIGHT NOTICE
2.2 ERRATA
2.3 COMMENTS
3. REFERENCES
3.1 NORMATIVE REFERENCES
3.2 INFORMATIVE REFERENCES
4. DEFINITIONS AND ABBREVIATIONS
4.1 DEFINITIONS
4.2 ABBREVIATIONS
5. CACHING MODEL
5.1 WAP USER AGENT RESPONSIBILITIES
5.1.1 Interaction with the User Agent History Mechanism
5.1.2 Intra-Resource Navigation
5.2 WAP GATEWAY RESPONSIBILITIES
5.2.1 Time-of-Day
5.2.2 Caching Proxy
6. TIME OF DAY CLOCK
6.1 TOD REQUESTS
6.2 USER AGENT TOD CLOCK
7. SECURITY CONSIDERATIONS
1. Scope
Wireless Application Protocol (WAP) is a result of continuous work by the WAP Forum to define an industry-wide specification for developing applications that operate over wireless communication networks. The scope of the WAP Forum is to define a set of specifications to be used by wireless communication device service applications. The wireless market is growing very quickly and reaching new customers and services. To enable operators and manufacturers to meet the challenges in advanced services, differentiation and fast/flexible service creation, WAP defines a set of protocols in transport, session and application layers. For additional information on the WAP architecture, refer to « Wireless Application Protocol Architecture Specification » [WAP].
2. Document Status
This document is available online in the following formats:
• PDF format at http://www.wapforum.org/.
2.1 Copyright Notice
© Copyright Wireless Application Forum Ltd, 1999 all rights reserved.
Terms and conditions of use are available from the Wireless Application Protocol Forum Ltd. Web site at
http://www.wapforum.org/docs/copyright.htm.
2.2 Errata
Known problems associated with this document are published at http://www.wapforum.org/.
2.3 Comments
Comments regarding this document can be submitted to the WAP Forum in the manner published at http://www.wapforum.org/.
3. References
3.1 Normative References
[NTP] « Network Time Protocol, Version 3, Specification Implementation and Analysis », D. Mills,University of Delaware, March 1992. URL: ftp://ftp.isi.edu/in-notes/rfc1305.txt
[RFC2068] « Hypertext Transfer Protocol – HTTP/1.1 », R. Fielding, et al., January 1997. URL:
ftp://ftp.isi.edu/in-notes/rfc2068.txt
[RFC2119] « Key words for use in RFCs to Indicate Requirement Levels », S. Bradner, March 1997. URL:
ftp://ftp.isi.edu/in-notes/rfc2119.txt
[WAE] « Wireless Application Environment Specification », WAP Forum, 30-April-1998. URL:
http://www.wapforum.org/
[WAP] « Wireless Application Protocol Architecture Specification », WAP Forum, 30-April-1998. URL:
http://www.wapforum.org/
[WSP] « Wireless Session Protocol », WAP Forum, 30-April-1998. URL: http://www.wapforum.org/
3.2 Informative References
[WML] « Wireless Markup Language », WAP Forum, 30-April-1998. URL: http://www.wapforum.org/
4. Definitions and Abbreviations
4.1 Definitions
The following are terms and conventions used throughout this specification.
The key words « MUST », « MUST NOT », « REQUIRED », « SHALL », « SHALL NOT », « SHOULD », « SHOULD NOT », »RECOMMENDED », « MAY » and « OPTIONAL » in this document are to be interpreted as described in [RFC2119].Cache – a device’s local store of response messages and the subsystem that controls its message storage, retrieval and deletion. A cache stores cachable responses in order to reduce the response time and network bandwidth consumption on future, equivalent requests.
5. Caching Model
The WAP caching model is based on HTTP/1.1 caching as defined in [RFC2068]. In addition, a number of extensions and clarifications have been specified to facilitate the operation of HTTP/1.1 caching on limited function devices.This document applies to all WAP user agents, including those with no cache (ie, a zero byte cache).
5.1 WAP User Agent Responsibilities
The user agent MUST faithfully implement resource caching as described in [RFC2068].
5.1.1 Interaction with the User Agent History Mechanism
The interaction between the user agent cache and the WML history is controlled by the Cache-control: mustrevalidate header. When going « back » to a URI (e.g., a WML PREV task), the user agent should attempt to use the cached resource. The browser must support the following interaction between cached resources and the WML..
Si le lien ne fonctionne pas correctement, veuillez nous contacter (mentionner le lien dans votre message)Wireless application protocol security considerations (112 KO) (Cours PDF)
