MW needs full etag support, with hooks for extensions. Without it, we can't
widely support caching in the case you've outlined.
Different browsers handle the Vary header differently. Some treat Varies
as "don't cache." Chrome (possibly other webkit browsers) treats it as a
marker to revalidate w
On Thu, 12 Apr 2012 12:54:41 -0700, Arthur Richards
wrote:
On Thu, Apr 12, 2012 at 12:43 PM, Daniel Friesen
wrote:
Might this be a browser caching issue, not a server caching issue?
Yeah, I believe so.
As a temporary hack you could try updating the *_LoggedOut cookie when
you
chang
On Thu, Apr 12, 2012 at 12:43 PM, Daniel Friesen
wrote:
>
>
> Might this be a browser caching issue, not a server caching issue?
>
Yeah, I believe so.
> As a temporary hack you could try updating the *_LoggedOut cookie when you
> change the view cookie to invalidate previous cached pages.
Intr
On Thu, 12 Apr 2012 12:18:21 -0700, Arthur Richards
wrote:
Per bug 35842, I've overhauled the persistent cookie handling in the
MobileFrontend extension. I think my changes will work fine on the WMF
architecture where most of our sites have a separate domain for their
mobile version. However,
Per bug 35842, I've overhauled the persistent cookie handling in the
MobileFrontend extension. I think my changes will work fine on the WMF
architecture where most of our sites have a separate domain for their
mobile version. However, for sites that use a shared domain for both
desktop and mobile v
