You're
Looks like my WebKit browser is the reason.
Safari 4 and Firefox 3 do not show this behaviour. I know that Safari
is a WebKit based browser but I'm talking about the WebKit browser
itself.
Tracing the element loading in Safari 4 shows the far future expires
header as expected.
We
This is odd, it should be working out of the box. Perhaps the browser
is the problem here.
On Thu, Jun 4, 2009 at 11:25 AM, Joachim Van der Auwera
wrote:
> Have you switched off production mode?
Perhaps in 5.1, in dev mode we won't specify the far future expires
header. In 5.1 I'm pretty sure th
Have you switched off production mode?
Joachim
Moritz Gmelin wrote:
Hi,
after updateing our application to T5.1 I was hoping for noticeable
accelleration in loading of pages. However while checking the log
output I can see that all the assets are requested from the browser on
every loading
Hi,
after updateing our application to T5.1 I was hoping for noticeable
accelleration in loading of pages. However while checking the log
output I can see that all the assets are requested from the browser on
every loading of a page for example I can see this
INFO: Request time: 0 ms, pag
