fixed list numbering
converted to 1.6 markup
|Deletions are marked like this.||Additions are marked like this.|
|Line 17:||Line 17:|
| * [http://www.ietf.org/rfc/rfc2616.txt RFC 2616 (text)]
* [http://www.w3.org/Protocols/rfc2616/rfc2616.html RFC 2616 (HTML)]
* [http://www.w3.org/Protocols/HTTP/1.1/rfc2616.pdf RFC 2616 (PDF)]
| * [[http://www.ietf.org/rfc/rfc2616.txt|RFC 2616 (text)]]
* [[http://www.w3.org/Protocols/rfc2616/rfc2616.html|RFC 2616 (HTML)]]
* [[http://www.w3.org/Protocols/HTTP/1.1/rfc2616.pdf|RFC 2616 (PDF)]]
|Line 23:||Line 23:|
|* [http://www.ietf.org/rfc/rfc1945.txt RFC 1945 (text)]||* [[http://www.ietf.org/rfc/rfc1945.txt|RFC 1945 (text)]]|
|Line 37:||Line 37:|
|* [http://www.ietf.org/rfc/rfc2965.txt RFC 2965 (text)]||* [[http://www.ietf.org/rfc/rfc2965.txt|RFC 2965 (text)]]|
|Line 40:||Line 40:|
|* [http://www.ietf.org/rfc/rfc2964.txt RFC 2964 (text)]||* [[http://www.ietf.org/rfc/rfc2964.txt|RFC 2964 (text)]]|
|Line 43:||Line 43:|
|* [http://www.ietf.org/rfc/rfc2109.txt RFC 2109 (text)]||* [[http://www.ietf.org/rfc/rfc2109.txt|RFC 2109 (text)]]|
|Line 46:||Line 46:|
|* [http://wp.netscape.com/newsref/std/cookie_spec.html Persistent Client State HTTP Cookies] [[BR]] It's called a ''Preliminary Specification'' since it was never finalized. Don't worry, this is the actual specification.||* [[http://wp.netscape.com/newsref/std/cookie_spec.html|Persistent Client State HTTP Cookies]] <<BR>> It's called a ''Preliminary Specification'' since it was never finalized. Don't worry, this is the actual specification.|
|Line 62:||Line 62:|
|* [http://www.ietf.org/rfc/rfc2617.txt RFC 2617 (text)]||* [[http://www.ietf.org/rfc/rfc2617.txt|RFC 2617 (text)]]|
|Line 65:||Line 65:|
|* [http://davenport.sourceforge.net/ntlm.html]||* [[http://davenport.sourceforge.net/ntlm.html]]|
|Line 83:||Line 83:|
|* [http://www.ietf.org/rfc/rfc2817.txt RFC 2817 (text)]||* [[http://www.ietf.org/rfc/rfc2817.txt|RFC 2817 (text)]]|
|Line 86:||Line 86:|
|* [http://www.ietf.org/rfc/rfc2818.txt RFC 2818 (text)]||* [[http://www.ietf.org/rfc/rfc2818.txt|RFC 2818 (text)]]|
|Line 99:||Line 99:|
|* [http://www.ietf.org/rfc/rfc1867.txt RFC 1867 (text)]||* [[http://www.ietf.org/rfc/rfc1867.txt|RFC 1867 (text)]]|
|Line 107:||Line 107:|
|* [http://www.ietf.org/rfc/rfc2396.txt RFC 2396 (text)]||* [[http://www.ietf.org/rfc/rfc2396.txt|RFC 2396 (text)]]|
|Line 112:||Line 112:|
|* [http://www.ietf.org/rfc/rfc3143.txt RFC 3143 (text)]||* [[http://www.ietf.org/rfc/rfc3143.txt|RFC 3143 (text)]]|
This page lists the specifications that are or could be relevant for the design and implementation of HttpClient 4.0.
The Hypertext Transfer Protocol (HTTP) is the only protocol directly supported by HttpClient. The current version of the protocol is 1.1, specified by RFC 2616. Version 1.1 maintains backward compatibility with version 1.0, specified by RFC 1945. RFC 1945 is obsoleted by RFC 2616, but still relevant for compatibility.
- RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1
- RFC 1945: Hypertext Transfer Protocol -- HTTP/1.0 (obsoleted by RFC 2616)
Cookies are the primary means for servers to maintain sessions with clients. They were originally introduced by Netscape, later standardized in RFC 2109, and reworked in RFC 2965. RFC 2109 is obsoleted by RFC 2965, but still relevant for compatibility. Netscape cookies do not conform to the standardized formats, but are relevant as well because they are still used frequently. RFC 2964 documents best practices for using cookies.
- RFC 2965: HTTP State Management Mechanism
- RFC 2964: Use of HTTP State Management
- RFC 2109: HTTP State Management Mechanism (obsoleted by RFC 2965)
- Netscape Cookies
Persistent Client State HTTP Cookies
It's called a Preliminary Specification since it was never finalized. Don't worry, this is the actual specification.
Servers can ask clients to authenticate before accessing specific resources or performing restricted operations. The standard authentication mechanisms are Basic and Digest, both specified in RFC 2617. Also frequently used is NTLM, a proprietary protocol for which no complete specification is publicly available.
TLS or SSL with client authentication is not handled as part of HTTP. See the section on "Secure Communication" for TLS or SSL.
- RFC 2617: HTTP Authentication: Basic and Digest Access Authentication
- NTLM: NT LAN Manager Authentication
HTTP communication can be encrypted for confidentiality. Netscape developed the original technology called SSL (Secure Sockets Layer) for this purpose. SSL was later enhanced and standardized as TLS (Transport Layer Security) in RFC 2246. TLS is backward compatible with SSL. As the name suggests, encryption is handled on a protocol layer below HTTP. HttpClient does not implement TLS nor SSL, it just allows to use them if available.
RFC 2817 specifies the CONNECT method to establish HTTP tunnels through proxies. Such tunnels can then be switched to secure communication. RFC 2818 describes how to use HTTP over TLS connections.
RFC 1867: Form-based File Upload in HTML
RFC 1867 specifies the MIME type application/x-www-form-urlencoded for sending data from web formulars to HTTP servers. While content encoding itself is not in the scope of HttpClient, posting form data is a requirement. HttpClient needs to provide a mechanism to use an external encoder for generating message bodys with this encoding.
RFC 2396: Uniform Resource Identifiers (URI): Generic Syntax
RFC 2396 specifies the primary format for addressing resources on HTTP servers and elsewhere. HttpClient needs to be able to handle the format used for addressing HTTP servers.