Last modified: 2014-10-16 20:08:37 UTC
Example with X-CS: 250-99: https://ru.m.wikipedia.org/w/api.php?format=json&action=zeroconfig&type=config returns {"enabled":true,"id":"250-99","showImages":true,"whitelistedLangs":["ru","en"],"enableHttps":false,"sites":["m.wikipedia","zero.wikipedia"]} This result is cached for just 10 minutes, while the zero config isn't changed anywhere as frequently. The total number of requests doesn't look very scary - 447k requests last month, however it will be growing steadily. I wonder if making it a ResourceLoader module would make the situation any better though - we'll need some way to vary the modules by X-CS and that would require either the URLs to be unique or us to vary Zero load.php requests by X-CS (and mess with bits to add that header) - neither sounds particulary attractive.
I think this was fixed a while ago, and besides, zero will soon (hopefully) switch to unified design, which means that every zero request will pull Special:ZeroRatedMobileAccess to insert banned & config in one go. https://www.mediawiki.org/wiki/Requests_for_comment/Unfragmented_ZERO_design
(In reply to Yuri Astrakhan from comment #1) > I think this was fixed a while ago, and besides, zero will soon (hopefully) > switch to unified design, which means that every zero request will pull > Special:ZeroRatedMobileAccess to insert banned & config in one go. > > https://www.mediawiki.org/wiki/Requests_for_comment/Unfragmented_ZERO_design Yuri: So does keeping this ticket still open make sense?
