Include a useful error message when a null byte is found in the URL path #1811
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.
Why?
There are reports of cryptic 400 errors when PHP users include null bytes in API urls. We're not sure why this happens with PHP more often than other languages, but it seems to be the case.
Because we can't customize the error on the server side, we raise a more proactive error in the SDK to help users self-debug their issues.
What?
$absUrl
right before making a requestSee Also