| Summary: | [SOUP] Does not reuse TCP connection for POST fetch requests | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | laurence.ejraee | ||||
| Component: | WPE WebKit | Assignee: | Nobody <webkit-unassigned> | ||||
| Status: | RESOLVED MOVED | ||||||
| Severity: | Normal | CC: | bugs-noreply, laurence.ejraee, mcatanzaro, pgriffis | ||||
| Priority: | P2 | ||||||
| Version: | Other | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Linux | ||||||
| Attachments: |
|
||||||
|
Description
laurence.ejraee
2023-07-18 05:54:24 PDT
Can you confirm that this is built with libsoup2 or libsoup3 and what version of libsoup? Also does the website use HTTP/2 or HTTP/1.1 (you can enable the Protocol column in the inspector). This issue is could be one of libsoup and not WPE. Also maybe a real world example that you can find is helpful. Just testing it in the wild here (with libsoup 3 and HTTP/2) and the connection was shared. This is built with libsoup2 version 2.62.3. Looking at the inspector the website is using HTTP/1.1 as request states: POST /stg/v1.0/create-authcode HTTP/1.1 and response states: HTTP/1.1 200 OK I'll see if I can find real world example and update. Thanks. Ah I can confirm that libsoup does not share for POST requests: https://gitlab.gnome.org/GNOME/libsoup/-/blob/d1509188ebd2219db1a147e9d77ffd5b4d161a2e/libsoup/soup-connection-manager.c#L399 I think this issue should be moved there. Thanks for the very quick and valuable feedback, I'll move to libsoup. Kind regards. |