Validate proxy IP headers and use SHA-256 for request fingerprinting#1
Draft
Validate proxy IP headers and use SHA-256 for request fingerprinting#1
Conversation
This file contains hidden or 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
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.
Motivation
Description
ip()to trim and validateHTTP_CF_CONNECTING_IP,HTTP_X_REAL_IP, and the leftmost entry ofHTTP_X_FORWARDED_FORwithfilter_var(..., FILTER_VALIDATE_IP)and only return them when valid.REMOTE_ADDRbefore returning and fall back to the literal'0.0.0.0'when it is missing or invalid.fingerprint()by ensuringqueryandbodyare arrays beforeksort, replacemd5calls withhash('sha256', ...)for query, body, json and the final fingerprint, and handlejson_encodepossibly returning false by defaulting to an empty string.Testing
phpunit, and all tests completed successfully.Codex Task