Change Details

From @ori on IRC: > firefox is doing SPDY coalescing probably and is buggy in that it tries the lookup over the existing IPv6 connection despite geoiplookup.wm.org having no AAAA. to reproduce you have to first open a SPDY session e.g. with en.wp.org. starting a browser and opening geoiplookup.wm.org would work, but opening the main site first, then quickly opening a tab with geoiplookup would fail (return Geo { IPv6:true } )

From @ori on IRC: > firefox is doing SPDY coalescing probably and is buggy in that it tries the lookup over the existing IPv6 connection despite geoiplookup.wm.org having no AAAA. to reproduce you have to first open a SPDY session e.g. with en.wp.org. starting a browser and opening geoiplookup.wm.org would work, but opening the main site first, then quickly opening a tab with geoiplookup would fail (return Geo { IPv6:true } ) From @faidon on IRC: > faidon@oxygen:~$ wc -l ~/geoiplookup-20151218 > 4541 /home/faidon/geoiplookup-20151218 > faidon@oxygen:~$ jq '.ip' ~/geoiplookup-20151218 | grep -c : > 5 > faidon@oxygen:/srv/log/webrequest/archive$ zcat sampled-1000.json-20151218.gz |wc -l > 8546007

From @ori on IRC: > firefox is doing SPDY coalescing probably and is buggy in that it tries the lookup over the existing IPv6 connection despite geoiplookup.wm.org having no AAAA. to reproduce you have to first open a SPDY session e.g. with en.wp.org. starting a browser and opening geoiplookup.wm.org would work, but opening the main site first, then quickly opening a tab with geoiplookup would fail (return Geo { IPv6:true } ) From @faidon on IRC: > faidon@oxygen:~$ wc -l ~/geoiplookup-20151218 > 4541 /home/faidon/geoiplookup-20151218 > faidon@oxygen:~$ jq '.ip' ~/geoiplookup-20151218 | grep -c : > 5 > faidon@oxygen:/srv/log/webrequest/archive$ zcat sampled-1000.json-20151218.gz |wc -l > 8546007