-
Notifications
You must be signed in to change notification settings - Fork 205
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
Skip Cache Flag for API (?) #2314
Comments
It sounds a little weird to me :-) Generally, it's the responsibility of the server to decide when to use the cache (for DDoS attacks, for example). Also, if the cache is well-implemented on the server side, you should never see a difference as a client ! |
Yeah this is just for debugging purposes... Not sure what the best soln is though. |
The cache is global, so it is weird for one user to be able to bypass it. (Would the cache be updated in that case?) |
yep! when a user does not use a cache he penalizes other users by consuming more server resources for the same result.. this is not serious when there are few users but it remains strange that a user can decide to make a server work more :) (in that case we can decide to update the cache or not) |
See #2783 |
No description provided.
The text was updated successfully, but these errors were encountered: