Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Policy::Caching: issues when can't connect to backend. #1163

Merged
merged 1 commit into from
Feb 18, 2020

Conversation

eloycoto
Copy link
Contributor

@eloycoto eloycoto commented Feb 12, 2020

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]

@eloycoto eloycoto requested a review from a team as a code owner February 12, 2020 14:07
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]>
@eloycoto eloycoto merged commit 3616bc4 into master Feb 18, 2020
@eguzki eguzki deleted the THREESCALE-4471 branch October 23, 2023 08:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants