Always include Content-Transfer-Encoding #127
Open
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.
Content-Transfer-Encoding does not appear to be enforced in requests, only in responses [1]
That said, it does appear in an example of client enrollment in the spec [2].
Testing with server http://testrfc7030.com/ does not require Content-Transfer-Encoding in the request. Test server set up with globalsign/est [3] does require the header and will fail enrollment without it.
[1] https://datatracker.ietf.org/doc/html/rfc7030
[2] https://datatracker.ietf.org/doc/html/rfc7030#appendix-A.3
[3] https://github.com/globalsign/est