Fix invalidation not being triggered for some status codes #230
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
Fix #224. Invalidation was not triggered when the controller response had status code 204 or 302.
ddeboer
force-pushed
the
fix-invalidation-status-codes
branch
from
292bffd to
3f6cda3
Compare
dbu
added a commit
that referenced
this pull request
Jul 13, 2015
…-codes Fix invalidation not being triggered for some status codes
|
thanks a lot! |
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.
Fix #224. Invalidation was not triggered when the controller returned a response with status codes such as 204 or 302. A more elaborate solution, which involves creating separate, configurable response matchers (as well as request matchers), as described in #69, should be done in a separate PR.