Answer the question
In order to leave comments, you need to log in
How to solve the problem of saving pictures for users?
Guys, such a problem, we have a big dbo with old icons, we drew new ones, put them in, but they didn’t change for users, as they are saved in the cache. Forcing 15k users to clear the cache is not really an option. We decided to add something like an identifier to the links to the icons, the user enters, sees a new link and a picture on it and loads it, but after we have implemented it, tests are pouring in. The team is not big, so the question is, what are the options for solving such a problem? At least give me an idea.
Answer the question
In order to leave comments, you need to log in
option 1 - pragma but cache and header management - plus - a solution for all css images in one fell swoop, minus - in the future, nifiga will not be cached, which is not buzzing.
option 2 - after the name of the requested file, put the get request tag "?" and a random key (a number or a piece of a hash from a file), then these files will be re-requested from the server every time the get parameter changes. Plus - the files will always be up to date and will not stretch again. Minus - everywhere you need to embed a storka with an additional code. The problem is especially relevant for CSS.
when you change in html:
<img src="images/first.png" alt="">
<img src="images/first.png?ver2" alt="">
.selector {
background: url('img/first.png') no-repeat;
}
.selector {
background: url('img/first.png?ver2') no-repeat;
}
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question