[01:59] <wgrant> The build queue has finally caught up.
[02:00] <sarnold> \o/
[20:21] <KenSharp> launchpad.net didn’t send any data.
[20:21] <KenSharp> Cannot log in
[20:21] <KenSharp> bugs.launchpad.net didn’t send any data.
[20:22] <KenSharp> or even get the damned thing to load
[20:22] <sarnold> working fine here; maybe try mtr to try to spot problems?
[20:23] <KenSharp> 0% packet loss
[20:24] <KenSharp> it's not like it's uncommon
[20:26] <sarnold> hmm... "didn't send any data" sounds vaguely familiar -- any chance this is firefox with privacy badger? I kept getting errors like that on discourse sites (never launchpad, though) back when I used to use privacy badger
[20:27] <KenSharp> Nope. Chrome.
[20:28] <sarnold> heh turns out my memory was pretty poor, it was saying protocol violation.. https://bugzilla.mozilla.org/show_bug.cgi?id=1716898
[20:30] <KenSharp> trying to log in is where the problem starts, apparently. after that every request fails.
[20:40] <KenSharp> cookie errors
[20:40] <KenSharp> This cookie was blocked because its path was not an exact match for a superdirectory of the requests url's path.
[20:40] <KenSharp> This cookie was blocked because neither did the request URL's domain exactly match the cookie's domain, nor was the request URL's domain a subdomain of the cookie's Domain attribute value.
[20:44] <KenSharp> So it's setting invalid cookies
[21:05] <cjwatson> All looks fine here.  launchpad.net sets a cookie with Domain: .launchpad.net, which is valid
[21:07] <cjwatson> Just tried in Chrome 101.0.4951.64 in an incognito window to make sure I was logging in from scratch; all fine