Switching from HTTP/1.1 to HTTP/2 breaks static resource loading

[hamadodene]

Description

I tried setting up a listener with HTTP/2, with my backend also configured to support HTTP/2 requests.
However, when making requests, some JS and CSS files are not fully loaded, and I see many errors in the browser console.
Unfortunately, I cannot share the full details, but when switching back to HTTP/1.1, the issue does not occur.

---

Steps to Reproduce

1. Configure a backend with JS + CSS that supports HTTP/2 and SSL.
2. In Carapace, configure the backend with:
   • backend.x.ssl.enable=true
   • Set cacertificate and cacertificatepath for the truststore.
3. Set up your listener with SSL (HTTP/2 is enabled by default).
4. Make some requests

---

Expected Behavior

All JS and CSS files should load correctly over HTTP/2 without errors.

---

Actual Behavior

Some JS and CSS files fail to load, and multiple errors appear in the browser console.
When switching to HTTP/1.1, the issue disappears.

---

Environment

• Carapace version: actual master
• OS: Oracle linux 9
• Backend type: tomcat

---

Additional Context

The issue only occurs with HTTP/2 and does not happen with HTTP/1.1.