Feature Request: Support for http2 / http3

Christian_S · March 30, 2024, 9:59pm

I've seen that http1.1 is used to delivery the content.

Can http2 / http3 offered as an option to enable if required?

BR Christian

DL6ER · March 31, 2024, 6:10am

What would be the benefit?

To me, HTTP/2 doesn't seem to be addressing any relevant problems and would not bring any noticeable improvements to Pi-hole while it'd be a whole lot of work to get it implemented. Mainly, HTTPS/2 seems to address performance issues for bad connections, at the cost of considerably more complex algorithms in server and client. Bad connections between you and your Pi-hole shouldn't be a problem.

Please check this issue for the status of HTTP/2 development in the webserver we are embedding: CivetWeb - the last update was almost two years go...

github.com/civetweb/civetweb

HTTP/2 design considerations

opened 03:32PM - 25 May 20 UTC

bel2125

The HTTP2 standard is available for some time now, and the first request to supp…ort is on the TODO list since ~3 years. Unfortunately including a third party library (like suggested in #324) seemed to be not feasible. Even a library has a compatible license (MIT), it must also have a compatible architecture. Existing applications should work with little to no changes. "No change" would be possible only with a HTTP1-to-HTTP2-proxy approach. There is no meaning to include this directly into CivetWeb, as there are already existing stand-alone proxies for this. "Little changes" means, it should keep the existing structure with registering callbacks and sending the HTTP response messages there. The callback should not need to know, if the client uses HTTP/1.x or HTTP/2. I did not find an existing solution for this, that could be smoothly integrated into the CivetWeb source. Thus, it was required to create several prototypes to find a way this could work. In this issue I want to explain some design details and collect feedback.