You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's assume we want to load some image from barberry with no cache on client side.
That can be done easily with GET /SomeHash_100x100?{randomNumber} for example GET /SomeHash_100x100?1528962263
But for now we will cache image everytime with all different randomNumber we will pass.
That can lead to increase of used space for cache.
My suggestion is no to take into view GET parameters at all when you're creating cache file, since we do not handle any GET parameters anyhow, and we for sure will return same result no matter what GET parameters you will pass.
The text was updated successfully, but these errors were encountered:
I wonder why you wanted to disable cache at client side. There is no way to replace a document in barberry by a different one. This makes cache always valid.
Let's assume we want to load some image from barberry with no cache on client side.
That can be done easily with
GET /SomeHash_100x100?{randomNumber}
for exampleGET /SomeHash_100x100?1528962263
But for now we will cache image everytime with all different
randomNumber
we will pass.That can lead to increase of used space for cache.
My suggestion is no to take into view GET parameters at all when you're creating cache file, since we do not handle any GET parameters anyhow, and we for sure will return same result no matter what GET parameters you will pass.
The text was updated successfully, but these errors were encountered: