hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Httpcomponents Wiki] Update of "HttpClientTutorial" by OlegKalnichevski
Date Mon, 09 Mar 2009 20:04:07 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Httpcomponents Wiki" for change notification.

The following page has been changed by OlegKalnichevski:
http://wiki.apache.org/HttpComponents/HttpClientTutorial

------------------------------------------------------------------------------
  
  == Request execution ==
  
+ === HTTP requests ===
+ 
+   GET, HEAD methods. Entity enclosing POST and PUT methods.
+ 
  === Working with message headers ===
  
    Populating request headers.
@@ -36, +40 @@

    
  === Ensuring release of resources ===
  
-   Always consume content or abort the request.
+   Always consume content fully or abort the request to ensure connection release.
  
  === Response handlers ===
  
@@ -53, +57 @@

  == HTTP execution context ==
  
    Maintaining processing state. Persisting state between request executions using local
context.
+   
+ == HTTP protocol interceptors ==
+ 
+    HTTP protocol customization using custom protocol interceptors
  
  == HTTP parameters ==
  
@@ -97, +105 @@

  
    Hostname verifier implementations.
  
- === DNS name resolution ===
- 
-   Implementing custom DNS name resolution.
- 
  = HTTP state management =
  
+ == HTTP cookies ==
+ 
+   Cookie versions. cookie properties; cookie origin.
+   
+ == Cookie specs ==
+ 
+ === Netscape draft ===
+ 
+   Should be avoided unless absolutely necessary for compatibility with legacy code
+ 
+ === RFC 2109 ===
+ 
+   Older version of the standard supreceded by RFC 2965.
+ 
+ === RFC 2965 ===
+   
+   The standard way of managing HTTP state. Still not very well supported and commonly used.
+ 
+ === Browser compatiblity ===
+   
+   Garbage in - garbage out.
+ 
+ === Best match ===
+   
+   Picks up a cookie spec based on the properties of the HTTP request.
+   
+ == Choosing cookie policy ==
+ 
+   HTTP client level cookie policy can be overriden on the HTTP request level if required.
+ 
+ == Custom cookie policy ==
+ 
+   Implementing custom CookieSpec.
+ 
  = HTTP authentication =
  
+ == User credentials ==
+   
+   Basic username / password. NTLM credentials. Credentials providers. Credentials store.
+   
+ == Authentication schemes ==
+ 
+ === Basic ===
+   
+    Well, basic authetication. Suits best TLS/SSL encrypted communication.
+ 
+ === Digest ===
+   
+    Digest authetication. More secure than Basic.
+ 
+ === NTLM authentication ===
+   
+    Windows platform specific. Believed to be more secure than Digest. Supported only partially

+    through an external engine (JCIFS).
+    
+ == Choosing authetication policy ==
+ 
+   HTTP client level authetication policy can be overriden on the HTTP request level if required.
+ 
+ == Authentication handling ==
+ 
+   Custom authentication handling.
+ 
+ == Preemptive authetication ==
+ 
+   Must be used with care. Requires custom protocol interceptors. 
+ 
  = Redirect handling =
  
- = Trouble-shooting =
+   Redirects are handled automatically, except those explicitly prohibited by the HTTP spec.

+   Redirects on POSTs and PUTs are converted to GET.
+   
+ == Redirect handler ==
  
+   Custom redirect handling.
+ 
+ = Advanced topics =
+ 
+ == Stateful connections ==
+ 
+   Pooling stateful connections. User tokens. 
+ 
+ === User token handler ===
+   
+   Custom user token handling.
+   
+ == DNS name resolution ==
+ 
+   Custom DNS name resolution.
+ 
+ == Custom HTTP connections ==
+ 
+   Replacing the standard HTTP connection implementation with a custom one.
+ 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


Mime
View raw message