[ENHANCEMENT] Using HTTP/2 instead of HTTP/1.1

[daffainfo]

Is there an existing issue for this?

• I have searched the existing issues and discussions.

Enhancement Description

There are a lot of raw request that still using HTTP/2 in their request instead of HTTP/1.1

Use Case / Problem

-

Proposed Solution

Change all http version from HTTP/2 to HTTP/1.1

Alternatives Considered

No response

Additional Context

No response

[princechaddha]

@daffainfo could you please share the reason behind the requested changes? We usually add templates after proper validation, and making such changes might break some of them. However, if there’s a solid reason to proceed without affecting any existing templates, we can consider doing so. Thanks

[daffainfo]

@princechaddha we usually use HTTP/1.1 for each raw request, you can find them with github search (3k results vs 54 results)

im not sure why this change will "break" the templates. And also not all of the website using HTTP/2 u know

[princechaddha]

@daffainfo, the comment about potentially breaking templates referred to making mass changes after templates have already been validated and merged.

We generally avoid unnecessary mass updates unless absolutely required as there can be many edge cases specific to the template.

That said, I agree that not all websites use HTTP/2 and updating all templates to HTTP/1.1 would still be accepted by HTTP/2 servers. Theoretically, there could be some misconfigured or non-standard servers that accept only HTTP/2 but such cases would violate the RFC and are extremely rare. HTTP/2 mainly offers performance benefits for multiple requests due to multiplexing over HTTP/1.1 that is another reason.

For now I’ve raised a PR with the changes. The team will validate a few HTTP/2 templates to ensure there are no unexpected edge cases with specific applications