Skip to content

Conversation

@msieurtoph
Copy link

The behaviors of 'x-apicache-force-fetch' and 'x-apicache-bypass' have become the same for no reason.
This commit restores the original behavior of 'x-apicache-force-fetch' which was to force data fetch AND update the cache with new data ... while 'x-apicache-bypass' completely bypasses the apicache middleware.

The behaviors of 'x-apicache-force-fetch' and 'x-apicache-bypass' have become the same for no reason.
This commit restores the original behavior of 'x-apicache-force-fetch' which was to force data fetch AND update the cache with new data ... while 'x-apicache-bypass' completely bypasses the apicache middleware.
@coveralls
Copy link

coveralls commented Aug 7, 2020

Coverage Status

Coverage remained the same at 97.531% when pulling 3886acf on msieurtoph:patch-1 into f27cb2b on kwhitley:master.

@msieurtoph
Copy link
Author

CI errors have nothing to do with my commit ... :(

@msieurtoph msieurtoph changed the title Restores the original behavior of 'x-apicache-force-fetch' header Restore the original behavior of 'x-apicache-force-fetch' header Aug 10, 2020
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