When you set a background image (you could possibly include using an img tag as well - I haven't tested that though) in Google Chrome and the server isn't asking for it to be cached, Google Chrome will hit the server asking for the image again (even if it's already in the page - I had filed this as a bug, but it was set as wontfix). Is there a way that I could circumvent this (preferably using jQuery)?
I have loaded the image into a javascript Image object (as the plan is to place it on canvas) so I thought I could do something with that (but Set an Image object as a div background image using javascript states otherwise).
Setting the server to ask the browser to cache the file isn't ideal as it is dynamically generated (I know about the ?_rand=123 trick, but would prefer a pure client side solution).