Comment 7 for bug 409466

On Aug 12, 2009, at 5:34 AM, <email address hidden> wrote:

>
> I checked Karl this morning with IE6 and what I'm seeing is
> everything still has the Vary header. That means every page request
> is reloading more than 500k of javascript files. Fortunately many
> actions don't actually result in a full page reload: when you just
> reload the content panel everything is fine, but going to a page
> like /people that is a fresh page results in 33 requests for css,
> js, and images.

Hmm, that's very (no pun intended) surprising and geesh, I bet the
performance feels awful in IE6.

Is it possible that the is changing the User Agent when it sends the
request to KARL? We are using user agent sniffing in Apache to remove
the header.

Stated differently, are you able to test with and without your proxy,
just so we can possibly eliminate it from the equation?

> The problem is that I used an https: url to access Karl: when I use
> http: then there is no Vary: header and the static content is
> cached, when I use https: there is a Vary: header.

Ah HA, I wonder if there is something messed up in our vhost config.

> BTW, I see that every response for static content includes a Set-
> Cookie header. Is that deliberate? I think it will prevent the proxy
> servers from ever caching the static content so everyone's browser
> has to retrieve their own copy.

Hmm, interesting point. We made a change, late in the game, to have
the app server (BFG) send back static resources instead of Apache. It
is adding the cookie automatically due to repoze.who.

We'll see if we can't fix that.

> That may be bad in a poorly connected office, but on the other hand
> without it the proxy servers could cache static content requested by
> Firefox (with the Vary header) and then serve it up to IE users (who
> shouldn't get the Vary): the fix of course would be to include
> "Vary: User-Agent" whenever the Vary header is set.

Do you have any offices using a proxy besides the Oxford office?

--Paul