-
commit-queue@webkit.org authored
https://bugs.webkit.org/show_bug.cgi?id=95747 PR199729 Patch by Otto Derek Cheung <otcheung@rim.com> on 2012-09-04 Reviewed by Rob Buis. Internally Reviewed by Joe Mason. If the browser has never saved a secure protocol cookie in its mapping before, and it tries to set and retreive a secure cookie over a non-secure protocol, it will not show up because the link between the secure and non-secure mapping isn't created until a cookie (sent through secure) is set. The fix is to also check for the linkage in getRawCookies. Note that we cannot map the secure CookieMap to the non-secure one because getRawCookies is a const function. Manually tested using our Browser Test suite. * platform/blackberry/CookieManager.cpp: (WebCore::CookieManager::getRawCookies): git-svn-id: http://svn.webkit.org/repository/webkit/trunk@127470 268f45cc-cd09-0410-ab3c-d52691b4dbfc
commit-queue@webkit.org authoredhttps://bugs.webkit.org/show_bug.cgi?id=95747 PR199729 Patch by Otto Derek Cheung <otcheung@rim.com> on 2012-09-04 Reviewed by Rob Buis. Internally Reviewed by Joe Mason. If the browser has never saved a secure protocol cookie in its mapping before, and it tries to set and retreive a secure cookie over a non-secure protocol, it will not show up because the link between the secure and non-secure mapping isn't created until a cookie (sent through secure) is set. The fix is to also check for the linkage in getRawCookies. Note that we cannot map the secure CookieMap to the non-secure one because getRawCookies is a const function. Manually tested using our Browser Test suite. * platform/blackberry/CookieManager.cpp: (WebCore::CookieManager::getRawCookies): git-svn-id: http://svn.webkit.org/repository/webkit/trunk@127470 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Loading