diff --git a/src/docbkx/statemgmt.xml b/src/docbkx/statemgmt.xml index 6367605a2..bbe081455 100644 --- a/src/docbkx/statemgmt.xml +++ b/src/docbkx/statemgmt.xml @@ -40,22 +40,22 @@ compliance.
HTTP cookies - Cookie is a token or short packet of state information that the HTTP agent and the + An HTTP cookie is a token or short packet of state information that the HTTP agent and the target server can exchange to maintain a session. Netscape engineers used to refer to it as a "magic cookie" and the name stuck. - HttpClient uses Cookie interface to represent an - abstract cookie token. In its simples form an HTTP cookie is merely a name / value pair. + HttpClient uses the Cookie interface to represent an + abstract cookie token. In its simplest form an HTTP cookie is merely a name / value pair. Usually an HTTP cookie also contains a number of attributes such as version, a domain for which is valid, a path that specifies the subset of URLs on the origin server to - which this cookie applies, and maximum period of time the cookie is valid for. - SetCookie interface represents a + which this cookie applies, and the maximum period of time for which the cookie is valid. + The SetCookie interface represents a Set-Cookie response header sent by the origin server to the HTTP agent in order to maintain a conversational state. - SetCookie2 interface extends SetCookie with + The SetCookie2 interface extends SetCookie with Set-Cookie2 specific methods. - ClientCookie interface extends + The ClientCookie interface extends Cookie interface with additional client specific - functionality such ability to retrieve original cookie attributes exactly as they were + functionality such as the ability to retrieve original cookie attributes exactly as they were specified by the origin server. This is important for generating the Cookie header because some cookie specifications require that the Cookie header should include certain attributes only if they were @@ -105,8 +105,8 @@ stdCookie.setAttribute(ClientCookie.PORT_ATTR, "80,8080");
Cookie specifications - CookieSpec interface represents a cookie management - specification. Cookie management specification is expected to enforce: + The CookieSpec interface represents a cookie management + specification. The cookie management specification is expected to enforce: rules of parsing Set-Cookie and optionally @@ -147,7 +147,7 @@ stdCookie.setAttribute(ClientCookie.PORT_ATTR, "80,8080"); Browser compatibility: - This implementations strives to closely mimic (mis)behavior of common web + This implementation strives to closely mimic the (mis)behavior of common web browser applications such as Microsoft Internet Explorer and Mozilla FireFox. @@ -167,7 +167,7 @@ stdCookie.setAttribute(ClientCookie.PORT_ATTR, "80,8080");
HTTP cookie and state management parameters - These are parameters that be used to customize HTTP state management and behaviour of + These are parameters that be used to customize HTTP state management and the behaviour of individual cookie specifications: @@ -193,7 +193,7 @@ stdCookie.setAttribute(ClientCookie.PORT_ATTR, "80,8080"); Cookie request header. Otherwise, each cookie is formatted as a separate Cookie header. This parameter expects a value of type java.lang.Boolean. If this - parameter is not set the choice of a default value is CookieSpec + parameter is not set, the choice of a default value is CookieSpec implementation specific. Please note this parameter applies to strict cookie specifications (RFC 2109 and RFC 2965) only. Browser compatibility and netscape draft policies will always put all cookies into one request @@ -205,7 +205,7 @@ stdCookie.setAttribute(ClientCookie.PORT_ATTR, "80,8080"); 'http.protocol.cookie-policy': defines the name of a cookie specification to be used for HTTP state management. This parameter expects a value of type - java.lang.String. If this parameter is not set + java.lang.String. If this parameter is not set, valid date patterns are CookieSpec implementation specific. @@ -215,7 +215,7 @@ stdCookie.setAttribute(ClientCookie.PORT_ATTR, "80,8080");
Cookie specification registry HttpClient maintains a registry of available cookie specifications using - CookieSpecRegistry class. The following specifications are + the CookieSpecRegistry class. The following specifications are registered per default: @@ -269,11 +269,11 @@ httpget.getParams().setParameter(
Custom cookie policy In order to implement a custom cookie policy one should create a custom implementation - of CookieSpec interface, create a + of the CookieSpec interface, create a CookieSpecFactory implementation to create and initialize instances of the custom specification and register the factory with HttpClient. Once the custom specification has been registered, it can be activated the - same way as the standard cookie specifications. + same way as a standard cookie specification. 'http.cookie-store': - CookieStore instance represents the actual + CookieStore instance representing the actual cookie store. The value of this attribute set in the local context takes precedence over the default one. The local HttpContext object can be used to customize - the HTTP state management context prior to request execution or examine its state after + the HTTP state management context prior to request execution, or to examine its state after the request has been executed: Per user / thread state management One can use an individual local execution context in order to implement per user (or - per thread) state management. Cookie specification registry and cookie store defined in + per thread) state management. A cookie specification registry and cookie store defined in the local context will take precedence over the default ones set at the HTTP client level.