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

some confusion about x-apicache-force-fetch & x-apicache-bypass #53

Closed
Red-Lv opened this issue Dec 6, 2016 · 1 comment
Closed

some confusion about x-apicache-force-fetch & x-apicache-bypass #53

Red-Lv opened this issue Dec 6, 2016 · 1 comment

Comments

@Red-Lv
Copy link

Red-Lv commented Dec 6, 2016

I find the two header have the same effect. what's the purpose of this two different headers?
And at the same time, the x-apicache-force-fetch header will make the server block because it does not call next()。

@msieurtoph
Copy link

msieurtoph commented Aug 7, 2020

@Red-Lv (and anyone interested in those headers ;) )

The original behaviors were not the same.
Take a look at this PR : #220

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

No branches or pull requests

2 participants