Custom headers with the CLI option --header
#28
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.
These changes add a command-line option
--header
, e.g.--header 'Access-Control-Allow-Origin: *'
.Basic tests are included for this option.
When accepting the argument, a very simple sanitization is made, the string is required to contain
": "
, and can’t contain a'\n'
character. These checks are far from what is required to truly validate a HTTP header, but will at least detect simple mistakes and forbid the abuse of having arguments that include more than one header, or, worse, that include a body for the response (after"\r\n\r\n"
).This should also close the Issue #16 and PR #27, I think, since CORS functionality can be obtained by specifying a custom header.