[09:02:00] why is my $('li#ca-edit a').text('source'); since recently being overwritten by something? [10:07:42] ContentTranslation-servers seems dead, anything known about that? [10:25:00] Hello. Are there any issues? 208.80.152.0/22 seems to have dropped off the routing table. [11:09:40] krd: according to ops, related to a recent network maint, should be fully recovered [11:09:47] (but why do people leave before I can answer them?) [11:13:24] oh I missed this [11:15:11] he probably left because it was very transient [11:15:17] so transient that he shouldn't had seen it at all [11:15:26] :D [21:42:30] hola [21:42:43] https://en.wikipedia.org/w/api.php?action=query&prop=extracts&format=json&exintro=&titles=New_York_City doesn't seem to be getting cached [21:43:01] even if I fetch with clean cookie jar [21:43:21] miss; miss; Age: 0 [21:44:06] is that because it won't get purges? [21:44:19] maybe it could at least support IMS? [21:45:15] jeremyb: long time no see! [21:46:46] ori: yeah, long ircbreak [21:46:49] hi :) [21:47:03] maxage=300 doesn't help with IMS [21:48:29] IMS = If-Modified-Since? [21:48:33] yes [21:49:03] let me double check what my browser's sending [21:49:12] but how could it help if it's miss; miss [21:50:38] the headers from mediawiki are 'Cache-control: private, must-revalidate, max-age=0' [21:50:49] that's when I curl the app server directly [21:51:31] I wonder why. The caching behavior of API responses is one of those perennial bug tracker topics that is impossible to follow. [21:51:39] but it's better cache-control with maxage= [21:51:57] i thought it was better than this [21:52:06] any tips on tickets to watch? [21:52:12] let's see [21:52:40] https://phabricator.wikimedia.org/T100262 [21:52:49] this is related to http://wm-bot.wmflabs.org/browser/index.php?start=08%2F11%2F2015+19%3A58%3A24&end=08%2F11%2F2015+21%3A31%3A24&display=%23wikidata [23:22:09] bye... maybe back to hibernation