Decode binary in GET requests. Closes #98. #114
Merged
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.
This patch add decoding of base64-encoded messages in PKIOperation queries.
Tested against juniper (junos 20.1) client and found working. Juniper behaviour slightly
differs from already proposed idea:
a) it does not encodes all messages with base64, only PKIOperation. For example,
with GetCACert query looks like path="/scep?operation=GetCACert&message=CA-CERT-NAME"
(not encoded), and attempt to decode such string will lead to decoding failure (may be
GetCACert is not considered as binary, and only binary data shall be encoded per rfc).
b) before decoding, messages are unescaped.