From 22a92de6d551c02e6117ef6f98d6cae692c1c54d Mon Sep 17 00:00:00 2001 From: "Torne (Richard Coles)" Date: Mon, 21 Oct 2019 14:34:03 -0400 Subject: Clarify CookieManager RFC reference. RFC2109 has been obsolete for a long time, and the docs aren't very clear what exactly the RFC has to do with CookieManager; the RFC is about HTTP and it's not immediately clear how this would apply to a Java API. Update the reference to the current cookie spec (and hyperlink it), and clarify the text to explain that the HTTP header formats from the RFC are the formats used to get/set set cookies. Fixes: 143086151 Test: make ds-docs Change-Id: I5e5838d3435b74516847b63e485fdd93810284aa --- core/java/android/webkit/CookieManager.java | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/core/java/android/webkit/CookieManager.java b/core/java/android/webkit/CookieManager.java index 23d12374453f..3824c22a40a7 100644 --- a/core/java/android/webkit/CookieManager.java +++ b/core/java/android/webkit/CookieManager.java @@ -22,7 +22,10 @@ import android.net.WebAddress; /** * Manages the cookies used by an application's {@link WebView} instances. - * Cookies are manipulated according to RFC2109. + *

+ * CookieManager represents cookies as strings in the same format as the + * HTTP {@code Cookie} and {@code Set-Cookie} header fields (defined in + * RFC6265bis). */ public abstract class CookieManager { /** -- cgit v1.2.3-59-g8ed1b