Caching with Firefox

Hi folks,

it seems that firefox keeps reloading css, javascript and images in
spite of the Expires header.
Anybody experiencing this problem? Google did not help.

Thanks: Balázs
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Hi!

> Hi folks,
>
> it seems that firefox keeps reloading css, javascript and images in
> spite of the Expires header.
> Anybody experiencing this problem? Google did not help.
>
> Thanks: Balázs

Btw, this is in the context of a Gjallar instance that we just set up at
krampe.se (a server in the US) so we kinda noticed since we have pretty
bad ping from the EU.

Balázs - did you check that I haven't shot ourselves in the foot with any
Seaside "overrides" etc? Like expiration stuff for example. I don't
*think* I have, but I am not sure. :)

regards, Göran

_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Hi again!

Ok, I think this is related to the Apache proxying I set up (which is
broken right now). I had "NoCache *" and that might cause problems. :)

Anyway, I don't have time right now to figure out how to get this working
- this is a jungle (proxying, rewriting, HTML maps, Seaside config etc
etc) and unfortunately I still use Apache 1.3.33 (so a lot of advice don't
fit I think).

If anyone has a setup working for apache 1.3.33 I am all ears. :) I am
already using mod_proxy and mod_rewrite for other stuff.

regards, Göran

_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

As a sidenote.

On searching the answer for our problem, I've read this post
http://lists.squeakfoundation.org/pipermail/seaside/2005-February/004448.html .
I created a WAComponent, which have a 100K byte long style method and
renders a  no-op link .

The request for that css, when refreshing the page in firefox, has an extra
Cache-Control max-age=0 header compared to the request sent, when
clicking on the no-op link.

I tried this with ie also: it was slow when refreshing, and fast when
clicking the link. So it behaved the same way as firefox did.

cheers, Balázs

On 12/20/06, Göran Krampe <[hidden email]> wrote: _______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside