Anil Gangolli wrote:
----- Original Message ----- From: "Allen Gilliland"
<[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, September 01, 2006 9:18 AM
Subject: Re: problems with 3.0 on IE
Anil Gangolli wrote:
I'm seeing several odd problems with 3.0 on IE 6 on my local build.
I seem to be getting stale versions of pages unless I load bypassing
the cache.
I don't see how the caching could be having a different affect from
one browser to the next. What do you mean "bypassing the cache"?
I mean forced reload which tells the browser to (a) ignore its local
cache (b) don't send an If-Modified-Since header.
gotcha.
It's possible it's just bad browser caching. I know that firefox can
be really tricky with browser caching if you aren't careful,
especially with feeds. I know for a fact that there are times in
firefox when it won't even sent a request for a page to check 304, it
will just automatically use the browser cache, although i haven't
figured out the exact conditions for that yet.
I haven't diagnosed it yet, but I suspect it is that we are not
responding properly to some IfModified-qualified requests.
That's possible, I never use IE so I can't say that everything is tested
as well in IE. I know that one thing that can cause problems with
if-modified headers is date conversions, if for some reason IE is doing
something even just a few milliseconds different from the application
that can cause the 304 checking to be wrong.
-- Allen
Note: There are no proxies or intermediate servers between the browser
and my dev Tomcat running on the same host.
Has anyone else seen this with IE on current 3.0 builds? I don't want
to hold anything up if it is a personal setup issue.
-- Allen
Is anyone else testing with IE?
I don't see the same problem with Firefox.
This is specific to 3.0. I'm not seeing this on 2.3.
I've just started looking into it, but hesitant to call this a
release candidate without it.
--a.
