ansaurus

Question

IE6 Not caching my images

Answer 1

+1 A:

see e.g. this question on how to control the caching settings for static file types.

Pekka 2010-10-18 11:42:33

@Pekka I posted above a sample of an image file from a Jquery UI Image. Is this what you are looking?

Mark Estrada 2010-10-18 11:53:52

@Mark yup. You need to change the server side settings for caching

Pekka 2010-10-18 11:54:38

@Pekka. Thanks. I will check out on this although I honestly dont have an idea yet on how to do this. I will ask for advise as I am still a beginner on Spring MVC

Mark Estrada 2010-10-18 12:29:25

You might have overlooked that his "Cache-Control" header was on the request, not the response. That's because he refreshed this page while doing the network capture. But the general advice is correct-- you need to set a freshness lifetime on this image. See http://www.fiddler2.com/redir/?id=httpperf

EricLaw -MSFT- 2010-10-18 13:56:06

Why would it be? That header is been set on the request, not on the response...

BalusC 2010-10-18 14:13:01

@BalusC @Eric (facepalm) of course. I must have been asleep. Cheers, I'll remove that bit

Pekka 2010-10-18 14:14:20

Answer 2

A:

Pekka is correct, its likely the caching control. A way around this would be to load your images from a different subdomain with a different set of cache headers. If you use a CDN provider, they will set the cache control for you.

IE SUCKS! id test it on IE 7-8-9. Very few use IE6 if its an intranet app, a quick fix would be Chrome frame, detect it, and if its not installed redirect to a download page.

franky b 2010-10-18 11:46:52

Answer 3

+2 A:

In all my JSP, I place below meta tag in all the head section. I did this because my apps relies heavily on Ajax and I need the latest copy of my web resource.

There are two problems:

The meta tags are ignored by the webbrowser. Put this information in the response header.
Even when it wasn't ignored, the meta rules would only apply on the HTML output of the JSP and thus not on all linked resources (img, js, css, etc) inside the HTML output. They have each their own rules in their own response header.

Your best bet is using a Filter which adds the Expires header on a far-future date on static content.

private static final long DEFAULT_EXPIRE_TIME = 604800000L; // ..ms = 1 week.

public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws ServletException, IOException {
    final long twoWeeksAhead = System.currentTimeMillis() + DEFAULT_EXPIRE_TIME;
    ((HttpServletResponse) response).setDateHeader("Expires", twoWeeksAhead);
    chain.doFilter(request, response);
}

Map this filter in web.xml on an url-pattern covering the URL of interest, e.g. /images/*.

BalusC 2010-10-18 14:19:02

+1 for specific advice

Pekka 2010-10-18 14:25:51

@Balusc Thanks. YSLOW grade for Expire now is A and I am seeing a considerable Load Time Speed Now in IE6. Thanks thanks!

Mark Estrada 2010-10-20 07:50:48

@Balusc On one thing, do you have an idea why only IE6 exhibits this kind of behavior? Why IE7/IE8/FF is doing fine..

Mark Estrada 2010-10-20 07:51:28

ansaurus

tags:

views:

answers:

IE6 Not caching my images

related questions