Ability to cache specified HTTP headers. (v2) #252
Merged
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
added 2 commits
February 11, 2019 16:36
… specified custom header is not set
|
@DGrudzynskyi , It looks like this hasn't made it into a nuget package release, but is something we could likely use too. Have you used this code to persist headers in production? |
|
@chuckwatson87 yes, I did. Although It was quite long time ago and I just don't remember whether there were any project-specific amendments, not posted back to this repo |
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.
Based on #126
But applied on top of latest version of dev branch with some changes:
IApiOutputCacheimplementation, if needed. No need for client code to worry about it.Also, there is a tiny fix for
Get_until25012015_1700test, as 2015 (and even 2018) has already passed by.