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.

Sign up for GitHub

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

Jump to bottom

HTTP/2 compatibility for ACME #431

Open
QuingKhaos opened this issue Oct 5, 2019 · 0 comments
Open

HTTP/2 compatibility for ACME #431

QuingKhaos opened this issue Oct 5, 2019 · 0 comments
Assignees
@QuingKhaos @timkimber
Labels
bug help wanted
Projects
bugfix

Comments

@QuingKhaos
Copy link
Collaborator

Q A
Bug? yes
New Feature? no
Version used 2.10 onwards

Actual Behavior

Should work with HTTP/2 on the ACME API, which was newly activated IIRC

Expected Behavior

Does fail on various places on lower-cased headers in the response due to HTTP/2, quick fix provided in #426

Possible Solutions

Fix all places dealing with response headers to be case insensitive like in #428
@QuingKhaos QuingKhaos self-assigned this Oct 5, 2019
@QuingKhaos QuingKhaos added this to Needs triage in bugfix via automation Oct 5, 2019
@QuingKhaos QuingKhaos moved this from Needs triage to High priority in bugfix Oct 5, 2019
@QuingKhaos QuingKhaos mentioned this issue Oct 5, 2019
Merged
1 task
@srvrco srvrco deleted a comment from github-actions bot Feb 27, 2020
@timkimber timkimber self-assigned this Feb 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@QuingKhaos QuingKhaos

@timkimber timkimber

Labels
bug help wanted
Projects
bugfix
  
High priority
Milestone
No milestone
Development

No branches or pull requests
2 participants
@QuingKhaos @timkimber