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

Ability to disable HTTP2 connections? #203

Closed
mspublic opened this issue Apr 8, 2024 · 3 comments · Fixed by #207
Closed

Ability to disable HTTP2 connections? #203

mspublic opened this issue Apr 8, 2024 · 3 comments · Fixed by #207

Comments

@mspublic
Copy link
Contributor

mspublic commented Apr 8, 2024

I may have missed the setting somewhere - but is it possible to disable HTTP2 (and 3) proxing via configuration? I would like to force all client/server connections to use HTTP1. If not is there a specific location you recommend we make the change in code?

Thanks!

@zh-jq-b
Copy link
Collaborator

zh-jq-b commented Apr 9, 2024

It's not possible yet.

To disable h2, you need to:

  • at TLS layer, remove h2 from ALPN and ALPS(boringssl) extension
  • at H2 layer, reset stream with error code HTTP_1_1_REQUIRED

H3 is still not supported yet.

@mspublic
Copy link
Contributor Author

mspublic commented Apr 9, 2024

Thanks @zh-jq-b we will investigate! We are needing to investigate/debug different streams/substreams which are easier to trace in HTTP1. I think this is a nice to have feature but I wouldn’t think it a high priority for most users yet.

@zh-jq-b
Copy link
Collaborator

zh-jq-b commented Apr 16, 2024

with #207 now you can set h2_inspect_policy: block in auditor config to block h2 traffic

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

Successfully merging a pull request may close this issue.

2 participants