🧹 [Maintenance]: Document reverse proxy workaround for SendEarlyHints

[grivera64]

Maintenance Task Description

Currently, the docs for Res.SendEarlyHints() specify that:

This feature requires HTTP/2 or newer. Some legacy HTTP/1.1 clients may not Early Hints (103 responses).

While the docs note the requirement for HTTP/2 in most cases, it doesn’t provide any direction on how to upgrade to HTTP/2.

This issue proposes to revise the docs to include instructions on how to use a reverse proxy to upgrade the http/1.1 responses to http/2 responses.

This can either be added as a separate section as a whole, or as a brief section under features that require this upgrade (e.g Early Hints).

Impact on the Project

Addressing this issue will ensure that users will have a sense of direction of ways to support Early Hints for browsers that only accept HTTP/2.

Additional Context (optional)

If we make an entire section for supporting HTTP/2 (or HTTP/3 if it supports it) from the client side, then we can list the several reverse proxies that will enable this and the related directive. These can include:

• nginx
• traefik

Otherwise, we can write that these reverse proxies support upgrading to HTTP/2.

Checklist:

• I have confirmed that this maintenance task is currently not being addressed.
• I understand that this task will be evaluated by the maintainers and prioritized accordingly.
• I am available to provide further information if needed.