summaryrefslogtreecommitdiffstats
path: root/net
diff options
context:
space:
mode:
authortyoshino@chromium.org <tyoshino@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-01-08 03:38:29 +0000
committertyoshino@chromium.org <tyoshino@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-01-08 03:38:29 +0000
commit3ffe71e020ea8e3597c2835f1ba0ebb8fb85ab9e (patch)
treefe9ac76dc74f86b0b9fbe803488ac1a9276e26f5 /net
parentd5a49e5ad3e6eb962cc026c9fd5c945f89ea9b0c (diff)
downloadchromium_src-3ffe71e020ea8e3597c2835f1ba0ebb8fb85ab9e.zip
chromium_src-3ffe71e020ea8e3597c2835f1ba0ebb8fb85ab9e.tar.gz
chromium_src-3ffe71e020ea8e3597c2835f1ba0ebb8fb85ab9e.tar.bz2
Reason:
Linux Builder (ChromiumOS) failed. http://chrome-buildbot.corp.google.com:8010/builders/Linux%20Builder%20(ChromiumOS)/builds/2050/steps/compile/logs/stdio Please add changes to external_cookie_handler_unittest.cc no to break compilation and reland? ---- Revert 35769 - Deleting cookies by setting the expires attribute on them with an empty value would not work in ChromeFrame with the host network stack enabled. When we receive a response in the host browser (IE) we send over the response headers which include the SetCookie header and a list of cookies retreived via the InternetGetCookie API. We call this API to retrieve the persistent cookies and send them over to Chrome. However this API returns session cookies as well as persistent cookies. There is no documented way to return only persistent cookies from IE. As a result we would end up setting duplicate cookies in Chrome, which caused this issu.e. To workaround this issue when we receive the response in the url request automation job which handles ChromeFrame network requests, we strip out duplicate cookies sent via InternetGetCookie. When a script deletes a cookie we now handle it correctly in IE and set the data to an empty string. However this does not delete the cookie. When such cookies show up in Chrome, we strip them out as well. Fixes bug http://code.google.com/p/chromium/issues/detail?id=30786 The changes to chrome_frame_npapi.cc/.h are to move the NPAPI functions to the chrome_frame namespace as they conflict with similar functions in NACL. Added the DeleteCookie function to the CookieStore interface, which I think missed out by oversight. Bug=30786 Test=Covered by ChromeFrame unit tests. I also added a unit test to test the newly added URLRequestAutomationJob::IsCookiePresentInCookieHeader function Review URL: http://codereview.chromium.org/518054 TBR=ananta@chromium.org Review URL: http://codereview.chromium.org/517070 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@35771 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'net')
-rw-r--r--net/base/cookie_store.h4
1 files changed, 0 insertions, 4 deletions
diff --git a/net/base/cookie_store.h b/net/base/cookie_store.h
index 1ea3fa2..e4d9b5d 100644
--- a/net/base/cookie_store.h
+++ b/net/base/cookie_store.h
@@ -59,10 +59,6 @@ class CookieStore : public base::RefCountedThreadSafe<CookieStore> {
return NULL;
};
- // Deletes the passed in cookie for the specified URL.
- virtual void DeleteCookie(const GURL& url,
- const std::string& cookie_name) = 0;
-
protected:
friend class base::RefCountedThreadSafe<CookieStore>;
virtual ~CookieStore() {}