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.
Description
The current option for customizing response headers is very limited, as demonstrated by #63 and #22. This pull request adds the possibility of specifying path-specific headers using a file (with the new
--headersfile
option).Design
The goal is to enable the possibility of testing complex headers behavior in a local environment. To this end, I have focused on adding support for two "real-world" header file formats:
Each of these formats uses a glob pattern-mathing system to specify the paths to which the headers should be applied. Additional file formats could be added in the future with minimal effort.
Additional notes
headers_test.dart
. It tests header parsing.sample/_headers
andsample/headers.json
. These files are also used in the tests.