-
public interface CookiePolicy
CookiePolicy implementations decide which cookies should be accepted and which should be rejected. Three pre-defined policy implementations are provided, namely ACCEPT_ALL, ACCEPT_NONE and ACCEPT_ORIGINAL_SERVER.See RFC 2965 sec. 3.3 & 7 for more detail.
- Since:
- 1.6
-
-
Field Summary
Fields Modifier and Type Field and Description static CookiePolicy
ACCEPT_ALL
One pre-defined policy which accepts all cookies.static CookiePolicy
ACCEPT_NONE
One pre-defined policy which accepts no cookies.static CookiePolicy
ACCEPT_ORIGINAL_SERVER
One pre-defined policy which only accepts cookies from original server.
-
Method Summary
Methods Modifier and Type Method and Description boolean
shouldAccept(URI uri, HttpCookie cookie)
Will be called to see whether or not this cookie should be accepted.
-
-
-
Field Detail
-
ACCEPT_ALL
static final CookiePolicy ACCEPT_ALL
One pre-defined policy which accepts all cookies.
-
ACCEPT_NONE
static final CookiePolicy ACCEPT_NONE
One pre-defined policy which accepts no cookies.
-
ACCEPT_ORIGINAL_SERVER
static final CookiePolicy ACCEPT_ORIGINAL_SERVER
One pre-defined policy which only accepts cookies from original server.
-
-
Method Detail
-
shouldAccept
boolean shouldAccept(URI uri, HttpCookie cookie)
Will be called to see whether or not this cookie should be accepted.- Parameters:
uri
- the URI to consult accept policy withcookie
- the HttpCookie object in question- Returns:
- true if this cookie should be accepted; otherwise, false
-
-
Document created the 11/06/2005, last modified the 04/03/2020
Source of the printed document:https://www.gaudry.be/en/java-api-rf-java/net/cookiepolicy.html
The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.
References
These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.