175189 2017-08-04 08:43:39 -0700 [SOUP] Too many redirections when loading google.com 2018-02-09 10:03:12 -0800 1 1 1 Unclassified WebKit WebKitGTK WebKit Nightly Build Unspecified Unspecified RESOLVED MOVED https://bugzilla.gnome.org/show_bug.cgi?id=792130 P2 Normal --- 1 christian webkit-unassigned bugs-noreply cedric.bellegarde cgarcia mcatanzaro oldest_to_newest 1335263 0 christian 2017-08-04 08:43:39 -0700 Using Epiphany 3.25.2 (with WebKit2 Gtk) and loading https://google.com results in a failure of the "notifications bubble" in the top right of the page. I can see the list of notifications available, but clicking the "popover" fails with an error in the console like: https://notifications.google.com/accounts/SetOSID?... Failed to load resource: Too many redirections If there is a better component to use for filing these sort of bugs, I'd be happy to set that on future bug reports. 1335382 1 mcatanzaro 2017-08-04 12:09:18 -0700 WebKitGTK+ was the best component to pick since it ensures we see it. This is a longstanding issue. Good to know it's the cause of the Google notifications problem too. *** This bug has been marked as a duplicate of bug 109576 *** 1363174 2 mcatanzaro 2017-10-22 15:03:57 -0700 Actually this doesn't seem like a duplicate. It's caused by blocking third-party cookies. If you muck with your cookie settings in Epiphany's preferences dialog, it should start working again. I noticed it when testing another redirection loop that I thought was an Epiphany bug, but which I could reproduce in Firefox. Firefox displayed a warning that sometimes loops can occur due to blocking cookies. So that's a bit surprising. Not sure what to do here. I guess it'll just have to remain broken. We want to be tightening cookie policy going forward, not loosening it. 1363293 3 cedric.bellegarde 2017-10-23 09:06:17 -0700 You are right, changing cookie policy fix the issue. 1363294 4 cedric.bellegarde 2017-10-23 09:09:35 -0700 As it works in Chrome and Firefox, I guess WebKit2.CookieAcceptPolicy.NO_THIRD_PARTY should check base domain name instead of netloc. If I visit plus.google.com, it should accept any google.com cookie request. Does it? 1363485 5 mcatanzaro 2017-10-23 17:27:12 -0700 (In reply to Cédric Bellegarde from comment #4) > As it works in Chrome and Firefox, I guess > WebKit2.CookieAcceptPolicy.NO_THIRD_PARTY should check base domain name > instead of netloc. What's netloc? Anyway no, the cookie is only allowed if the domain matches exactly, see soup_cookie_jar_add_cookie_with_first_party() which calls soup_cookie_domain_matches() which calls soup_host_matches_host(). > If I visit plus.google.com, it should accept any google.com cookie request. > Does it? Should it really? Is that how Safari works? We should match whatever Safari does. 1363577 6 cedric.bellegarde 2017-10-23 22:28:03 -0700 My girlfrien is using Safari on her Mac and notifications are working, but not sure third party cookies are blocked, will give a look this evening. Here, the issue is that for example, while opening notifications popover from plus.google.com, it does a request for a cookie from notifications.google.com and so WebKit blocks it. 1385126 7 mcatanzaro 2018-01-02 07:45:54 -0800 Moved to GNOME Bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=792130 1385346 8 mcatanzaro 2018-01-02 17:48:04 -0800 Unlikely coincidence that this happened today... but after working on bug #181231, I now have a layout test that I want to mark against this bug: http/tests/resourceLoadStatistics/grandfathering.html Reopening since we need an open WebKit bug for the test expectations. 1394860 9 mcatanzaro 2018-01-30 17:50:08 -0800 (In reply to Michael Catanzaro from comment #8) > Unlikely coincidence that this happened today... but after working on bug > #181231, I now have a layout test that I want to mark against this bug: > > http/tests/resourceLoadStatistics/grandfathering.html > > Reopening since we need an open WebKit bug for the test expectations. That's wrong, the problem in that test is unrelated. I'll reassign the expectation to some other bug. 1397990 10 mcatanzaro 2018-02-09 10:03:12 -0800 (In reply to Michael Catanzaro from comment #7) > Moved to GNOME Bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=792130 Should be fixed in libsoup. Please reopen if you have trouble with updated libsoup.