Hi! Recently I made a fix so that my uploaded images (stored in db) are cached.
I did this by returning status 304 (HTTP status not modified) as I found out that T5 handles asset requests in that way. But this means that the client has to perform a request for each asset/image. I thought that the adding of the application version to the assets url was there to inform clients when assets needed to be refetched and that they should be fetched from client cache (without a request) otherwise. For my images, the ideal would be as Howard pointed out to add a hashed signature to my image url:s and to cache them forever on client side. But as I found out T5 assets are not handled that way I skipped the hash code and just performed a check on the header "If-Modified-Since". What have I missed? Am I right when i say that T5 assets are handled with a request + 304 reply. Thanks in advance, Gunnar Eketrapp
