I'm not happy about how the (still relatively new) added feature for autologin works.
The new JS-based procedure replaces old the in-between page and its <img> loads.
This is a reminder to perform a back-to-back audit of it and clean or refactor it. Perhaps we can walk through it this September when I'm visiting the office.
It currently performs upto 55 network requests to get things set up:F or each of the entry points CA tries to hit (listed below) multiplied by the number of wiki projects (wikipedia, wikibooks, wiktionary, etc.)
- Special:CentralAutoLogin/start,
- Special:CentralAutoLogin/checkLoggedIn
- Special:CentralAutoLogin/createSession
- Special:CentralAutoLogin/validateSession
- Special:CentralAutoLogin/setCookies
See also
- Introduced in https://gerrit.wikimedia.org/r/58924 / 7a03ac9ac6c28
- Duplicate: T91196: Reduce calls to Special:CentralAutoLogin/checkLoggedIn
- Duplicate: T130935: CentralAutoLogin delays fully load time
- Bug: T202028: CentralAuth fails when using "site isolation" in Google Chrome and Chromium or "first-party isolation" in Firefox
- Prior perf work: T56195: CentralAuth not caching Special:CentralAutoLogin/start