Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When we are developing new sites or testing changes in new ones that involve css after the new code is committed and someone goes to check the changes they always see a cached version of the old css. This is causing a lot of problems in testing because people never are sure if they have the latest css on screen (I know shift and clicking refresh clears this cache but I can’t expect end users to know to do this). What are my possible solutions?
If you’re serving your CSS from static files (or anything that the query string doesn’t matter for), try varying that to ensure that the browser makes a fresh request, as it will think that it’s pulling a completley different resource, so have for example:
‘styles.css?token=1234’ in the CSS reference in your markup and change the value of ‘token’ on each CSS check-in