I don't work in Networking and Newton is not working on Chrome for Android anymore. Maybe Mike knows a good candidate (or is one).

Hello,

Could you please leave a feedback on how this issue tracking is going, since it is a bit urgent.

Thanks

Any detail about when this might have started happening?

+torne@

It started happening last month during some tests while accessing different CDNs

What version of WebView? Can you provide an app that reproduces the issue?

Version Chrome/50.0.2661.86

Unfortunately I cannot share an app because it has classified data within its URLs, but  you can easily try it out yourself by making an Apache website which returns a cookie with a path different than "path=/". Then when debugging it on remote in Chrome you can see that the said cookie is ignored.

Was there a previous version where it was working?

Unfortunately not, it is a very peculiar bug and we noticed it just lately

Can't reproduce this with webview 50.0.2661.86.

I threw up a trivial appengine app to try it:

1) http://robotic-parsec-130814.appspot.com/foobar/set sets a cookie "foo=bar" with path "/foobar"
2) http://robotic-parsec-130814.appspot.com/foobar/get displays the value of the "foo" cookie

Doing this with WebView worked fine - the correct cookie headers show up in network requests, and the stored cookie is visible (with the correct path) in devtools's cookie store tab as well.

So, unless you can provide more specific information on how to reproduce this, I don't think we can do anything. Either provide a server that we can test against, or an app that uses webview in a similar way to yours that can be pointed at a test server like the one I just put together, or both, to work out where the problem is.

Setting back to "unconfirmed" and unassigning for now until we have more info. (also removing myself from cc as I already get all webview issues mailed to me anyhow) :)

We've fixed the issue by setting the webview to accept third party cookies.

Could you explain a bit more? It's not clear whether your case should have been treated as a third party cookie or not, so even if enabling third party cookies fixes it for you, there may still be a bug in WebView.

Could you tell us what the URL of the page setting the cookie, and the path it was setting, were?

Thank you for providing more feedback. Adding requester "torne@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Actually I didn't know that all versions from Lollipop onward disabled third party cookies by default, and the CookieManager method to enable them is not intuitive enough. I tried out a lot of things and it turned out that CookieManager.getInstance().setAcceptThirdPartyCookies(*webview*, true) fixed the issue.

Right, but what I'm asking is, is the cookie you are setting actually a third party cookie? i.e. is it correct that it wasn't letting you set it? Just setting the path shouldn't make something third party, afaik.

robert.rausel: can you respond to torne's question?

Hi, sorry for the delay, got caught up in a lot of projects. It is indeed a third party cookie set directly from the CDN. It wasn't letting me set it until I added setAcceptThirdPartyCookies. Enabling this fixed it.

Thank you for providing more feedback. Adding requester "torne@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot