-
Notifications
You must be signed in to change notification settings - Fork 77
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
[Question]: Force cache #44
Comments
Hey @debo! You can use the GreedyCacheStrategy, introduced with #38. |
Hey @jeromegamez thanks for the head up, the documentation on here it's a bit meh unfortunately, I wasn't aware of that (read as I didn't even check the code to be honest :-P). I'll have a look into it thanks. |
@jeromegamez you made my day, that was amazing. Where do we have to sign to have this middleware integrated in the core? :D |
It already is :D |
@jeromegamez I meant this entire plugin to become part of GuzzleHttp core :) |
The documentation need some work 😄 (cf. #42). |
@debo can we close this issue? Have you able to use the GreedyCacheStrategy? |
@Kevinrob oh yes sorry, I forgot to update the issue. Thanks a lot. |
Is there a way with the current implementation to force the client to cache the response regardless the headers coming from the response? I would like to ask the response coming from an API but it is so badly implemented that it doesn't send back proper headers. What would be the best way to go about it?
The text was updated successfully, but these errors were encountered: