Talk:XFF project/Archives/2015
Latest comment: 9 years ago by Mattflaschen (WMF) in topic Google data compression proxies
 | Please do not post any new comments on this page. This is a discussion archive first created in 2015, although the comments contained were likely posted before and after this date. See current discussion or the archives index. |
Google data compression proxies
It looks like Google is operating what are effectively open proxy farms for Chrome mobile users: these do not seem to be on the XFF list. For an example of such a proxy, do a PTR lookup on 66.249.93.191. I cannot find any list of these on the web, or any way of deriving that list other than brute-force techniques. See [1], [2] and this talk page for more details. Given that Chrome is a major browser, this could potentially become a major problem if not fixed. -- The Anome (talk) 15:56, 16 November 2014 (UTC)
- Update: I've blocked 66.249.93.0/24 on enwiki, as the entire /24 appears to be nothing but these proxies. -- The Anome (talk) 19:55, 16 November 2014 (UTC)
- @The Anome: Relevant notes: "Secure connections (HTTPS) are routed directly from your mobile device to the destination, bypassing the compression proxy." So a lot of logged in traffic will not be affected. Erik Moeller (WMF) knows some people at Google. Maybe those contacts can help us get a list of the proxy IP ranges. Superm401 | Talk 06:25, 3 December 2014 (UTC)
- Thanks -- that's great. Do you know if any progress has been made on this? -- The Anome (talk) 14:16, 13 January 2015 (UTC)
- @The Anome: I haven't heard anything or contacted him further about this (I think I only pinged him above), so probably not. It may make sense to file a bug to track the issue. Mattflaschen (WMF) (talk) 05:08, 14 January 2015 (UTC)
- Thanks -- that's great. Do you know if any progress has been made on this? -- The Anome (talk) 14:16, 13 January 2015 (UTC)