It was a bug in Speed Tracer: http://code.google.com/p/speedtracer/issues/detail?id=20. Now fixed :)
On Jun 3, 3:24 pm, Dogan Narinc <[email protected]> wrote: > Thanks Brendan, > > I've posted a question on the Speed Tracer forum > here:https://groups.google.com/group/speedtracer/browse_thread/thread/ea74... > > On Jun 3, 2:45 pm, Brendan Kenny <[email protected]> wrote: > > > If you aren't able to get an answer here, this is the speedtracer > > google group:https://groups.google.com/group/speedtracer/topics > > > On Jun 3, 5:20 am, Dogan Narinc <[email protected]> wrote: > > > > Also worth to mention that the HTTP status is set to 200, which should > > > mean that it is not cached: > > > > Summary > > > [...] > > > From Cache false > > > Method GET > > > Http Status 200 > > > [...] > > > > On Jun 3, 11:07 am, Dogan Narinc <[email protected]> wrote: > > > > > Hi all, > > > > > Our server sets the ".nocache.js" files as non-cached when sent to > > > > browsers. Looking at them in Speed Tracer I can definitely see that > > > > the HTTP header is set as no-cache: > > > > > Response Headers > > > > [...] > > > > Pragma no-cache > > > > [...] > > > > Cache-Control no-cache, must-revalidate > > > > Expires Mon, 20 Dec 1998 01:00:00 GMT > > > > > And yet, Speed Tracer still shows the red "Critical" tag and says "GWT > > > > selection script '.nocache.js' file should be set as non-cacheable". > > > > > Is speed tracer looking at something else than pragma and cache- > > > > control to determine if a resource is set as cached? > > > > > I've posted this question here since I haven't been able to find a > > > > Speed Tracer forum, and I believe this is related to GWT too. > > > > > Cheers, > > > > > Dogan -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
