Skip to content

[bug] Parsed response incorrectly shows HTTP/1.1 when forcing HTTP/3 #2842

Description

@chanhanzhan

Describe the bug
When the "Force HTTP/3" option is enabled for sites that support HTTP/3, the actual HTTP/3 handshake completes successfully. However, the parsed response displayed in the application always incorrectly shows as HTTP/1.1.

To Reproduce
Steps to reproduce the behavior:

  1. Visit any website that supports HTTP/3.
  2. Enable the "Force HTTP/3 request" option.
  3. Observe the protocol version in the parsed response (it incorrectly displays as HTTP/1.1 despite a successful HTTP/3 handshake).

Expected behavior
The parsed response should correctly display HTTP/3 as the protocol version when a successful HTTP/3 handshake occurs.

Screenshots
(If applicable, add screenshots here)

Information

  • Platform: Linux
  • OS: Ubuntu 26.04
  • Arch: amd64
  • App Version: 3.2.17

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions