HTTP/2 compatiablity tracker

[marty1885]

This issue is used to track our HTTP/2 client's compatibility. Please comment here which endpoint(s) you are using so we can collect a list of know compatible endpoints. This issues will be closed upon HTTP/2 leaving beta. Currently known working hosts:

• google.com
• example.com
• clehaxze.tw (my blog, runs over nginx)
• http2cdn.cdnsun.com
• nasdaq.com
• www.nchc.org.tw
• amd.com
• archlinux.org
• openai.com
• cloudflare.com
• ietf.org
• generativelanguage.googleapis.com

[nqf]

Did I use it wrong?

export SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt

    auto client = HttpClient::newHttpClient("https://www.google.com");
    auto req = HttpRequest::newHttpRequest();
    client->sendRequest(
        req, [](ReqResult result, const HttpResponsePtr& response) {
            if (result != ReqResult::Ok) {
                std::cout
                    << "error while sending request to server! result: "
                    << result << std::endl;
                return;
            }

            std::cout << "receive response!:" << response->getBody() << std::endl;
        });

error while sending request to server! result: Bad response from server

[marty1885]

@nqf Ohh yeah... there 0is a bug in the HPACK decoder that fails to decode what we get from google.com. Let me debug it...

Update: The issue seems to be me not handling setting max table list size.. Checking the RFC

[marty1885]

@nqf Can you try #2045 ? I fixed it and confirmed it works on my machine. Turns our the issue is an unexpected empty path.

[nqf]

@marty1885 thanks， Confirmed that it can work