Observatory HTTPv2 Capabilities

[marius-peschke]

Dear Observatory developers,
When I have a webserver that only supports httpv2, I can't test its headers security with our local observatory instance.
Since it will not connect to any httpv2 only server.
As we strive to make more servers speak httpv2, we currently have to decide between staying on httpv1 or being able to test the headers.
Therefore i enter this feature request.
If possible also add HTTPv3 capabilities in the future.
Kindest Regards
Marius Peschke
University of Bern

[axelhahn]

As additional info:
We disabled http1 requests and send a 400 status, eg

curl -I --http1.1 "https://[servername]"
HTTP/1.1 400 Bad Request
Date: Mon, 20 Apr 2026 14:52:23 GMT
Server: Apache
Connection: close
Content-Type: text/html; charset=iso-8859-1

... but respond when using http2 (eg curl -I "https://[servername]")

Maybe the simplest solution is a visible element where the http version to use can be selected. Implementing an automatic detection can be tricky if a request sends a response with an error code and this is a wanted error response, eg 401 to force authentication.

Kind regards
Axel

[dipikabh]

Moving this to the observatory repo