Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTTP2 for non-https endpoints #4930

Closed
3 tasks done
mazzz1y opened this issue Sep 19, 2022 · 0 comments
Closed
3 tasks done

HTTP2 for non-https endpoints #4930

mazzz1y opened this issue Sep 19, 2022 · 0 comments

Comments

@mazzz1y
Copy link
Contributor

mazzz1y commented Sep 19, 2022

Prerequisites

  • I have checked the Wiki and Discussions and found no answer

  • I have searched other issues and found no duplicates

  • I want to request a feature or enhancement and not ask a question

Description

What problem are you trying to solve?

http2.0 not working for non-https endpoints

~ docker run -p3000:3000 -d adguard/adguardhome:v0.107.11 
~ curl -i --http2-prior-knowledge localhost:3000
curl: (16) Send failure: Broken pipe

Working example with another golang app

~ docker run -p8080:80 -d traefik
~ curl -i --http2-prior-knowledge localhost:3000
HTTP/2 404 
content-type: text/plain; charset=utf-8
x-content-type-options: nosniff
content-length: 19
date: Mon, 19 Sep 2022 10:24:37 GMT

404 page not found

It is required for some proxy configurations to avoid downgrading to http1.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants