Middleware to configure response headers #39
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.
Hi, first of thanks for this project I use it a lot :) !
This PR adds a middleware that lets you specify response HTTP Headers for certain paths and filetypes. With a JSON config that gets mounted into the container multiple header rules can be specified.
I added a documentation file for more info on how to use it.
Example config for implementing the caching best practices from gatsby.js :
Maybe take a closer look to the code as this is my first time programming in Go :) .
Would solve #24