[Webkit-unassigned] [Bug 259305] New: WebKit does not reuse TCP connection for POST fetch requests

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Jul 18 05:54:24 PDT 2023


            Bug ID: 259305
           Summary: WebKit does not reuse TCP connection for POST fetch
           Product: WebKit
           Version: Other
          Hardware: Unspecified
                OS: Linux
            Status: NEW
          Severity: Critical
          Priority: P2
         Component: WPE WebKit
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: laurence.ejraee at consult.red
                CC: bugs-noreply at webkitgtk.org

Created attachment 467066

  --> https://bugs.webkit.org/attachment.cgi?id=467066&action=review

Image showing TCP connection created again for another POST

On any version of wpewebkit, carrying out multiple POST fetch request does not reuse the TCP connection and instead creates a new connection for each request.
This occurs on wpewebkit 2.22, 2.28, and epiphany browser running WebKitGTK 2.38.6

For example with:
fetch('https://reqres.in/api/articles', {  method: "POST", body: JSON.stringify({ title: 'Fetch POST Request Example' }) });

On Chrome two calls to the above code reuse the connection from the first call.
On wpewebkit it is not reused.
[See image]

It is my understanding that persistent connections should be used here because the request and response headers have connection: keep-alive. Persistent connections should keep the TCP connection so that other fetches to the url can reuse the connection.

Question: Should multiple POST fetch requests reuse their connection like in Chrome or create a new connection for each request as seen?


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/20230718/0885ce6b/attachment-0001.htm>

More information about the webkit-unassigned mailing list