Yes, HTTP/2 requires HTTPS. It is technically possible to do H2 over HTTP, but nobody in the industry supports it, as there's no legitimate reason to. So for all practical purposes, yes, H2 requires HTTPS.
What's your URL? Are you requesting `http://foo` or `https://foo`? Needs to be https, as above. Second, what ports are you serving what protocols on, with ATS? What does your records.config proxy.config.http.server_ports look like? https://docs.trafficserver.apache.org/en/8.1.x/admin-guide/files/records.config.en.html#proxy-config-http-server-ports It should look something like: CONFIG proxy.config.http.server_ports STRING 80 80:ipv6 443:proto=http2;http:ssl 443:ipv6:proto=http2;http:ssl (Note the "proto=http" above refers to HTTP/1.1 versus HTTP/2, not HTTP versus HTTPS. The above "443:proto=http2;http:ssl" is saying "serve both HTTP/2 and HTTP/1.1 over SSL on port 443.") On Mon, Oct 4, 2021 at 12:41 PM Nick Dunkin <[email protected]> wrote: > Hi > > > > Disclaimer: I am very new to HTTP/2 so I may be making very basic > errors/assumptions here. > > > > I am trying to enable and test HTTP/2 on ATS 9.0.x. I am using CURL with > the “--http2-prior-knowledge” flag but I am not getting good results. > > > > From CURL I get the following error: > > * Recv failure: Connection reset by peer > > * Failed receiving HTTP2 data > > * Send failure: Broken pipe > > * Failed sending HTTP2 data > > * Connection #0 to host 10.211.55.6 left intact > > curl: (56) Recv failure: Connection reset by peer > > And from ATS I am seeing the following warnings in diags.log > > > > [Aug 22 15:45:22.334] [ET_NET 0] WARNING: Unregistered protocol type 1 > > > > One question I have is whether I need *HTTPS* to even be testing HTTP/2. > The internet seems a little vague on this question. > > > > Any pointers from the community would be most welcome. > > > > Thanks > > > > Nick > > > > *Nick Dunkin* > > Director, Software Engineering > > Manager – Architecture and New Product Introduction > > *o: * *+1 678.258.4071* > > *e:* [email protected] > > > > [image: [email protected]] > > >
