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

Add mechanism for user to disable HTTP/2 if required #1858

Closed
Tracked by #1139
ciarams87 opened this issue Apr 19, 2024 · 0 comments · Fixed by #1925
Closed
Tracked by #1139

Add mechanism for user to disable HTTP/2 if required #1858

ciarams87 opened this issue Apr 19, 2024 · 0 comments · Fixed by #1925
Assignees
Labels
enhancement New feature or request refined Requirements are refined and the issue is ready to be implemented. size/medium Estimated to be completed within a week
Milestone

Comments

@ciarams87
Copy link
Member

ciarams87 commented Apr 19, 2024

As a user of NGF
I want a way to disable HTTP/2 support in my NGF deployment
So that I can remove this support if security vulnerabilities are found in HTTP/2 functionality in NGINX

A/C:

  • A config option is provided so that HTTP/2 support can be disabled if required
  • If HTTP/2 is disabled and a GRPCRoute is deployed, the GRPCRoute's status is reported at Not Accepted.

Dev Notes:

  • This should likely be part of the NginxProxy CRD
This was referenced Apr 19, 2024
@mpstefan mpstefan added this to the v1.3.0 milestone Apr 22, 2024
@mpstefan mpstefan added enhancement New feature or request refined Requirements are refined and the issue is ready to be implemented. size/medium Estimated to be completed within a week labels Apr 22, 2024
@ciarams87 ciarams87 self-assigned this May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request refined Requirements are refined and the issue is ready to be implemented. size/medium Estimated to be completed within a week
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants