Policy::Caching: issues when can't connect to backend. #1163
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.
New HTTP-NG coroutines return 0 when can't connect, so the caching
policy fails on the second request used, because the cache status was
updated with the an invalid status
This changes makes sure that the response code is a valid one, so the
caching status will report correctly.
Fix: THREESCALE-4471
Reported-by:Jakub Smadis [email protected]
Signed-off-by: Eloy Coto [email protected]