[Webkit-unassigned] [Bug 222558] [SOUP] Request headers in web inspector are not what WebKit actually sent

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Mar 1 13:19:48 PST 2021


https://bugs.webkit.org/show_bug.cgi?id=222558

--- Comment #3 from Michael Catanzaro <mcatanzaro at gnome.org> ---
I don't trust the request method displayed either. I have a case where Firefox sends a POST request to some internal website, receives a 302 redirect response, and then sends a GET request to the new location. In contrast, the WebKit web inspector only shows WebKit making a GET request for the original request. It doesn't show the HTTP method used for the second request, but if I copy the request headers I can see it is doing POST when it should be GET. However, the server operator says they are really receiving GET for the second request, not POST! So I think WebKit is doing the right thing, but showing the wrong request method for both the first and second request when the redirect occurs.

This is a more complex issue than the example.com test, though, and it occurs on an internal domain that I can't share. I should set up a public test for it to see what is really happening. Anyway, treat it as a tangent: for the purposes of this bug, we should just ensure the web inspector displays HTTP/1.1. In the libsoup simple-httpd testcase, when I right-click the request in the web inspector and "Copy HTTP Request", the copied output is identical to what the server actually receives except for the missing HTTP/1.1.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20210301/e836e73b/attachment-0001.htm>


More information about the webkit-unassigned mailing list