Updated SHA256 Validation Utilities #13
Merged
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
added 2 commits
December 7, 2015 18:56
…s. Added SHA256 to headers constants in constants.js
zetlen
added a commit
that referenced
this pull request
Dec 10, 2015
Updated SHA256 Validation Utilities
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.
I refactored the SHA256 hash-stream.js utility to now add in a hash of the stringified request.body. I added a SHA256 constant to the headers in constants.js. And finally, I refactored is-request-valid.js to pull the date from request.headers, as well the headerPrefix and the SHA256 header constant to pull the SHA hash from the request.headers.