WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED MOVED
250734
[WPE][GTK] Cannot interact with github.com: the server responded with a status of 422 (Unprocessable Entity)
https://bugs.webkit.org/show_bug.cgi?id=250734
Summary
[WPE][GTK] Cannot interact with github.com: the server responded with a statu...
Michael Catanzaro
Reported
2023-01-17 15:59:34 PST
Since updating to WebKitGTK 2.39.4, it's no longer possible to interact with github.com using Ephy Tech Preview. I cannot post comments, change notification settings, etc. I see errors in the web inspector: [Error] Failed to load resource: the server responded with a status of 422 (Unprocessable Entity) (comment, line 0) This will make WebKit development quite inconvenient.
Attachments
Add attachment
proposed patch, testcase, etc.
Carlos Garcia Campos
Comment 1
2023-01-18 02:28:18 PST
I can't reproduce.
Michael Catanzaro
Comment 2
2023-01-18 08:44:49 PST
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....
Michael Catanzaro
Comment 3
2023-01-18 11:06:49 PST
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.
Michael Catanzaro
Comment 4
2023-01-18 11:11:58 PST
I deleted only the "user_session" cookie, signed in to GitHub again, and the problem is gone. Hm.
Michael Catanzaro
Comment 5
2023-01-22 07:07:12 PST
(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...?
Michael Catanzaro
Comment 6
2023-01-22 15:06:01 PST
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
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug