I saw your header, but couldn't tell that it was for tomorrow,
with the GMT time zone info. I don't read GMT go figure ;)
What I would recommend is trying to match the headers exactly
as when serving up the static file since we know that works,
oh and make sure the file extension is the same too. I saw your
URL for the modperl request as:
http://192.168.31.1/mediaexporter.pl/ef6880b34b91e817f8c9973f0e7efe10.png
... maybe IE is "smart" enough to see the .pl in the path and guess
that this is a dynamic request. If your URL looks more like:
http://192.168.31.1/mediaexporter/ef6880b34b91e817f8c9973f0e7efe10.png
that might help.(?) Best of luck. These browsers can be tough.
-- Joshua
_________________________________________________________________
Joshua Chamas Chamas Enterprises Inc.
NodeWorks >> free web link monitoring Huntington Beach, CA USA
http://www.nodeworks.com 1-714-625-4051
Ime Smits wrote:
>
> | In your Apache::ASP version, try setting Expires to tell IE
> | to cache explicitly...
> | $Response->{Expires} = 86400; # cache until tomorrow
>
> I did that. And and also tried
> $r->add_header('Expires',HTTP::Date::time2str(time+86400)); in a normal .pl
> file. In fact, the first header dump in my previous message shows the header
> doing it that way.
>
> Other things I tried:
>
> * "Cache-Control: public" (defaults to 'private' in Apache::ASP)
> * Killing the Cache-Control header all together
> * "Last-Modified:", tried in 5 minutes, in a month, in a year (the maximum
> according to HTTP/1.1 standards), somewhere in 2038.
> * "Expires:", idem dito
> * Minimal header (just content-type and length)
> * Telling IE (both 4.01 and 5.5) to *Never check*
>
> IMHO, that last one is the weirdest of all.
>
> Ime
