www/caddy: Add HTTP version selection. Mark NTLM as deprecated. #4071
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…etically, it only hard codes the transport http to versions 1.1. So, NTLM could be replaced by setting the http version to that value. At the same time, this also adds support for HTTP/3 to the upstream, which is included in the latest Caddy version 2.8.4 we have rolled out.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
versions 1.1astransport http_ntlmbefore the optionversionsintransport httpexisted. So, NTLM could be replaced by setting httpversions 1.1., since NTLM always requires the full header being sent. HTTPversions 2only sends the header one time, and that makes Outlook fail to authenticate.versions 3to the upstream, which is included in the latest Caddy version 2.8.4 we have rolled out.