provides a concrete implementation of a <code>CookieHandler</code>
and for most users is sufficient for handling HTTP state management.
<code>CookieManager</code> separates the storage of cookies from the policy surrounding,
accepting, and rejecting them. A <code>CookieManager</code> is initialized with a 
 and a 
. <code>CookieStore</code> manages the storage of the cookies. 
<code>CookiePolicy</code> makes policy decisions on cookie acceptance and rejection.
<p>
The following code shows how to create and set a system-wide CookieManager:

  java.net.CookieManager cm = new java.net.CookieManager();
  java.net.CookieHandler.setDefault(cm);
 
The first line calls the default <code>CookieManager</code> constructor to create 
the instance. The second line calls the static <code>setDefault</code> method 
of <code>CookieHander</code> to set the system-wide handler. 
<p>
The default <code>CookieManager</code> constructor creates a new 
<code>CookieManager</code> instance with a default cookie store and accept policy. 
<code>CookieStore</code> is the place where any accepted HTTP cookie is stored. 
If not specified when created, a <code>CookieManager</code> instance will use an 
internal in-memory implementation. This implementation is not persistent and 
only lives for the lifetime of the Java Virtual Machine. Users requiring a 
persistent store must implement their own store. 
<p>
The default cookie policy used by <code>CookieManager</code> is 
<code>CookiePolicy.ACCEPT_ORIGINAL_SERVER</code>, which only accepts cookies from 
the original server. So, the <code>Set-Cookie</code> response from the server must 
have a 	&#8220;domain&#8221; attribute set, and it must match the domain of the 
host in the URL.  For more information, see 
. Users requiring a different policy must implement the <code>CookiePolicy</code>
interface and pass it to the <code>CookieManager</code> constructor or set it to an already
constructed <code>CookieManager</code> instance by using the
<code>setCookiePolicy(cookiePolicy)</code> method.
<p>
When retrieving cookies from the cookie store, <code>CookieManager</code> also enforces 
the path-match rule from section 3.3.4 of
. So, a cookie must also have its
&#8220;path&#8221; attribute set so that the path-match rule can be applied before the 
cookie is retrieved from the cookie store.
<p>
In summary, <code>CookieManager</code> provides the framework for handling
cookies and provides a good default implementation for <code>CookieStore</code>.
<code>CookieManager</code> is highly customizable by enabling you to set your own 
<code>CookieStore</code>, <code>CookiePolicy</code>, or both.