| The following Internet specifications provide information relevant to the development and implementation of the servlet API and engines which support the servlet API: -
RFC 1630 Uniform Resource Identifiers (URI) -
RFC 1738 Uniform Resource Locators (URL) -
RFC 1808 Relative Uniform Resource Locators -
RFC 1945 Hypertext Transfer Protocol (HTTP/1.0) -
RFC 2045 MIME Part One: Format of Internet Message Bodies -
RFC 2046 MIME Part Two: Media Types -
RFC 2047 MIME Part Three: Message Header Extensions for non-ASCII text -
RFC 2048 MIME Part Four: Registration Procedures -
RFC 2049 MIME Part Five: Conformance Criteria and Examples -
RFC 2109 HTTP State Management Mechanism -
RFC 2145 Use and Interpretation of HTTP Version Numbers -
RFC 2324 Hypertext Coffee Pot Control Protocol (HTCPCP/1.0) [1] [1] This reference is mostly tongue-in-cheek although most of the concepts described in the HTCPCP RFC are relevant to all well-designed web servers. -
RFC 2616 Hypertext Transfer Protocol (HTTP/1.1) -
RFC 2617 HTTP Authentication: Basic and Digest Authentication You can locate the online versions of any of these RFCs at: http://www.rfc-editor.org/ The World Wide Web Consortium (http://www.w3.org/) is a definitive source of HTTP related information that affects this specification and its implementations . The Extensible Markup Language (XML) is utilized by the deployment descriptors described in this specification. More information about XML can be found at the following web sites: http://java.sun.com/ http://www.xml.org/ |