Prev: Another 301 redirect question-
Next: File (master page for aspx) does not exist on IIS 7
From: SleeplessAndy on 4 Jun 2010 07:48
Hi,


We have a site with some .js files that due to size/wan speed we want
to stay cached. Why could they be sticking around for about 10
different document loads, accessing the file, browsing away to other
pages, then back to similar docs using the file again, thenn suddenly
it gets deleted. The IE cache is set for testing to 5mb, and the file
sticks around, even though the cache continually goes up to this limit
and above, and other files are replaced. Then suddenly, a page load
will cause the large .js file to be removed, even though the expiry is
30 days in the future.

I don't understand. Any help gratefully received!

thanks

Andy
From: Richard Cornford on 4 Jun 2010 09:07
On Jun 4, 12:48 pm, SleeplessAndy wrote:
> Hi,
>
> We have a site with some .js files that due to size/wan speed
> we want to stay cached. Why could they be sticking around
> for about 10 different document loads, accessing the file,
> browsing away to other pages, then back to similar docs using
> the file again, thenn suddenly it gets deleted. The IE cache
> is set for testing to 5mb, and the file sticks around, even
> though the cache continually goes up to this limit and above,
> and other files are replaced. Then suddenly, a page load
> will cause the large .js file to be removed, even though
> the expiry is 30 days in the future.
>
> I don't understand. Any help gratefully received!

I don't know what you expect anyone to say about this. Caching is non-
mandatory and the rules that do apply to it may say a browser
shouldn't use a cached resource after it expires but they don't say
that it must not re-request a cached resource prior to its expiring.

The details of what IE is doing will be in the source code and/or
development documentation for the browser, so not available to anyone
outside Microsoft.

Richard.
From: SleeplessAndy on 4 Jun 2010 09:27
On 4 June, 14:07, Richard Cornford <Rich...(a)litotes.demon.co.uk>
wrote:
> On Jun 4, 12:48 pm, SleeplessAndy wrote:
>
> I don't know what you expect anyone to say about this. Caching is non-
> mandatory and the rules that do apply to it may say a browser
> shouldn't use a cached resource after it expires but they don't say
> that it must not re-request a cached resource prior to its expiring.
>
> The details of what IE is doing will be in the source code and/or
> development documentation for the browser, so not available to anyone
> outside Microsoft.
>
> Richard.

Ummm.. I didn't really 'expect' anyone to say anything in particular,
but perhaps offer some sort of reason why we are seeing this
behaviour. It isn't performing the same, it's apparently "random" but
this can't be the case.

The file is being deleted during an unrelated page load before it
expires, which is why it's being re-requested. Sometimes. It can
stay in the cache for 3 hours, 50 page loads, the go, then stay for 5
page loads, then go again.

I'm actually hoping for a onle line "Its this .... causing " really.
Fingers crossed.

From: Dan on 4 Jun 2010 09:36

"SleeplessAndy" <andybluestar(a)gmail.com> wrote in message
news:09e7751a-520c-430a-95f6-b3843a54d394(a)k39g2000yqb.googlegroups.com...
> Hi,
>
>
> We have a site with some .js files that due to size/wan speed we want
> to stay cached. Why could they be sticking around for about 10
> different document loads, accessing the file, browsing away to other
> pages, then back to similar docs using the file again, thenn suddenly
> it gets deleted. The IE cache is set for testing to 5mb, and the file
> sticks around, even though the cache continually goes up to this limit
> and above, and other files are replaced. Then suddenly, a page load
> will cause the large .js file to be removed, even though the expiry is
> 30 days in the future.
>
> I don't understand. Any help gratefully received!
>
> thanks
>
> Andy

If it's IE that is expiring this file, then that's an IE issue, not IIS,
assuming that IIS is sending the correct headers. Have you checked with
Fiddler2 or a similar tracing tool to see what the headers look like?

--
Dan

From: SleeplessAndy on 4 Jun 2010 09:55
On 4 June, 14:36, "Dan" <n...(a)worldofspack.com> wrote:

>
> If it's IE that is expiring this file, then that's an IE issue, not IIS,
> assuming that IIS is sending the correct headers. Have you checked with
> Fiddler2 or a similar tracing tool to see what the headers look like?
>
> --
> Dan- Hide quoted text -
>
> - Show quoted text -

You are right Dan, I posted this in here because I saw a similar(ish)
question when I searched for a solution. I'll repost in the correct
grou, but thanks for the tip, I'll follow that too. :)
 |  Next  |  Last
Pages: 1 2
Prev: Another 301 redirect question-
Next: File (master page for aspx) does not exist on IIS 7