An HttpCookie object represents an http cookie, which carries state
information between server and user agent. Cookie is widely adopted
to create stateful sessions.
toString()
Constructs a cookie header string representation of this cookie,
which is in the format defined by corresponding cookie specification,
but without the leading "Cookie:" token.
Constructs a cookie with a specified name and value.
The name must conform to RFC 2965. That means it can contain
only ASCII alphanumeric characters and cannot contain commas,
semicolons, or white space or begin with a $ character. The cookie's
name cannot be changed after creation.
The value can be anything the server chooses to send. Its
value is probably of interest only to the server. The cookie's
value can be changed after creation with the
setValue method.
By default, cookies are created according to the RFC 2965
cookie specification. The version can be changed with the
setVersion method.
Parameters:
name - a String specifying the name of the cookie
value - a String specifying the value of the cookie
Throws:
IllegalArgumentException - if the cookie name contains illegal characters
or it is one of the tokens reserved for use
by the cookie protocol
Constructs cookies from set-cookie or set-cookie2 header string.
RFC 2965 section 3.2.2 set-cookie2 syntax indicates that one header line
may contain more than one cookie definitions, so this is a static
utility method instead of another constructor.
Parameters:
header - a String specifying the set-cookie header.
The header should start with "set-cookie", or "set-cookie2"
token; or it should have no leading token at all.
Returns:
a List of cookie parsed from header line string
Throws:
IllegalArgumentException - if header string violates the cookie
specification's syntax, or the cookie
name contains llegal characters, or
the cookie name is one of the tokens
reserved for use by the cookie protocol
Specifies a comment that describes a cookie's purpose.
The comment is useful if the browser presents the cookie
to the user. Comments
are not supported by Netscape Version 0 cookies.
Parameters:
purpose - a String specifying the comment
to display to the user
Specifies a comment url that describes a cookie's purpose.
The comment url is useful if the browser presents the cookie
to the user. Comment url is RFC 2965 only.
Parameters:
purpose - a String specifying the comment url
to display to the user
Specifies the domain within which this cookie should be presented.
The form of the domain name is specified by RFC 2965. A domain
name begins with a dot (.foo.com) and means that
the cookie is visible to servers in a specified Domain Name System
(DNS) zone (for example, www.foo.com, but not
a.b.foo.com). By default, cookies are only returned
to the server that sent them.
Parameters:
pattern - a String containing the domain name
within which this cookie is visible;
form is according to RFC 2965
A positive value indicates that the cookie will expire
after that many seconds have passed. Note that the value is
the maximum age when the cookie will expire, not the cookie's
current age.
A negative value means
that the cookie is not stored persistently and will be deleted
when the Web browser exits. A zero value causes the cookie
to be deleted.
Parameters:
expiry - an integer specifying the maximum age of the
cookie in seconds; if zero, the cookie
should be discarded immediately;
otherwise, the cookie's max age is unspecified.
Specifies a path for the cookie
to which the client should return the cookie.
The cookie is visible to all the pages in the directory
you specify, and all the pages in that directory's subdirectories.
A cookie's path must include the servlet that set the cookie,
for example, /catalog, which makes the cookie
visible to all directories on the server under /catalog.
Consult RFC 2965 (available on the Internet) for more
information on setting path names for cookies.
Assigns a new value to a cookie after the cookie is created.
If you use a binary value, you may want to use BASE64 encoding.
With Version 0 cookies, values should not contain white
space, brackets, parentheses, equals signs, commas,
double quotes, slashes, question marks, at signs, colons,
and semicolons. Empty values may not behave the same way
on all browsers.
Returns the version of the protocol this cookie complies
with. Version 1 complies with RFC 2965/2109,
and version 0 complies with the original
cookie specification drafted by Netscape. Cookies provided
by a browser use and identify the browser's cookie version.
Returns:
0 if the cookie complies with the
original Netscape specification; 1
if the cookie complies with RFC 2965/2109
Sets the version of the cookie protocol this cookie complies
with. Version 0 complies with the original Netscape cookie
specification. Version 1 complies with RFC 2965/2109.
Parameters:
v - 0 if the cookie should comply with
the original Netscape specification;
1 if the cookie should comply with RFC 2965/2109
public static boolean domainMatches(String domain,
String host)
The utility method to check whether a host name is in a domain
or not.
This concept is described in the cookie specification.
To understand the concept, some terminologies need to be defined first:
effective host name = hostname if host name contains dot
or = hostname.local if not
Host A's name domain-matches host B's if:
their host name strings string-compare equal; or
A is a HDN string and has the form NB, where N is a non-empty
name string, B has the form .B', and B' is a HDN string. (So,
x.y.com domain-matches .Y.com but not Y.com.)
A host isn't in a domain (RFC 2965 sec. 3.3.2) if:
The value for the Domain attribute contains no embedded dots,
and the value is not .local.
The effective host name that derives from the request-host does
not domain-match the Domain attribute.
The request-host is a HDN (not IP address) and has the form HD,
where D is the value of the Domain attribute, and H is a string
that contains one or more dots.
Examples:
A Set-Cookie2 from request-host y.x.foo.com for Domain=.foo.com
would be rejected, because H is y.x and contains a dot.
A Set-Cookie2 from request-host x.foo.com for Domain=.foo.com
would be accepted.
A Set-Cookie2 with Domain=.com or Domain=.com., will always be
rejected, because there is no embedded dot.
A Set-Cookie2 with Domain=ajax.com will be accepted, and the
value for Domain will be taken to be .ajax.com, because a dot
gets prepended to the value.
A Set-Cookie2 from request-host example for Domain=.local will
be accepted, because the effective host name for the request-
host is example.local, and example.local domain-matches .local.
Constructs a cookie header string representation of this cookie,
which is in the format defined by corresponding cookie specification,
but without the leading "Cookie:" token.
The result is true only if two cookies
come from same domain (case-insensitive),
have same name (case-insensitive),
and have same path (case-sensitive).
Return hash code of this http cookie. The result is the sum of
hash code value of three significant components of this cookie:
name, domain, and path.
That is, the hash code is the value of the expression:
Submit a bug or feature For further API reference and developer documentation, see Java SE Developer Documentation. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples.