https://bugzilla.wikimedia.org/show_bug.cgi?id=43805

Krinkle <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
            Version|1.22-git                    |unspecified
           Keywords|platformeng                 |
          Component|General/Unknown             |General/Unknown
           See Also|https://bugzilla.wikimedia. |
                   |org/show_bug.cgi?id=37812,  |
                   |https://bugzilla.wikimedia. |
                   |org/show_bug.cgi?id=51766,  |
                   |https://bugzilla.wikimedia. |
                   |org/show_bug.cgi?id=54935   |
             Blocks|2114                        |
         Resolution|---                         |WORKSFORME
            Summary|ResourceLoader serving      |Outdated JS served for
                   |outdated JS                 |ext.echo modules
            Product|MediaWiki                   |Wikimedia
           Severity|critical                    |major

--- Comment #16 from Krinkle <[email protected]> ---
(In reply to comment #15)
> (In reply to comment #3)
> > The exact urls are cached for 30 days
> 
> Krinkle: Do you know where exactly this is defined/configured?

This is configured by $wgResourceLoaderMaxage['versioned']['server'].

However this number should not be modified. If anything, it could be made
bigger because the versioned urls are unique. If there is a newer version, the
client will know about it through the startup module and construct a different
url, thus avoiding the old cache. This is a central piece in the design of
resourceloader.

If a url has the correct version number but serves old content, it is likely
due to a race condition in the wmf deployment script where one server has the
new version, and within seconds another server still having the old version
gets a request for a module and thus serves it under the new timestamp. Thus
causing some cache servers to have the correct version and others the
incorrect, even though they are at the same url.

Anyway, to avoid these different generic "Outdated module served" bugs from
mixing up and being re-used in something that sounds equally generic, I'm
closing this one because it's several months old, the immediate problem was
solved, and there's no way to find out now that it was or whether a future bug
will be the same.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to