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

Always include Content-Transfer-Encoding #127

Open

kissen wants to merge 1 commit into cisco:main from kissen:always-send-content-transfer-encoding-in-requests

kissen commented Jan 30, 2024

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


          Always include Content-Transfer-Encoding

aad9cfb

* 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet