| Summary: | [WPE][GTK] Cannot interact with github.com: the server responded with a status of 422 (Unprocessable Entity) | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Michael Catanzaro <mcatanzaro> |
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED MOVED | ||
| Severity: | Normal | CC: | bugs-noreply, cgarcia, mcatanzaro |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
|
Description
Michael Catanzaro
2023-01-17 15:59:34 PST
I can't reproduce. I was hoping to bisect it, but I couldn't reproduce in my development environment, so I cleared all my website data for github.com and now the problem is gone. I'm still really suspicious because I've never seen this happen before until immediately after I upgraded to 2.39.4, but let's close this for now.... Two hours later, github.com is broken again, so reopening. This time I'll clear only one class of website data at a time until I figure out what is to blame. I'll start with cookies. I deleted only the "user_session" cookie, signed in to GitHub again, and the problem is gone. Hm. (In reply to Michael Catanzaro from comment #4) > I deleted only the "user_session" cookie, signed in to GitHub again, and the > problem is gone. Hm. I've been doing this roughly 2-4x per day. Is it really just me...? So this is not caused by WebKitGTK 2.39.4, but by a libsoup change that coincidentally landed in the same runtime update. That's pretty unlucky timing. https://gitlab.gnome.org/GNOME/libsoup/-/issues/330 |