<div dir="ltr">So there might be your answer - I guess "nv" stands for "netvision" - give them the URL and ask them to clear the cache for it.</div><div class="gmail_extra"><br><div class="gmail_quote">On 22 March 2015 at 05:56, Michael Tewner <span dir="ltr"><<a href="mailto:tewner@gmail.com" target="_blank">tewner@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I'm seeing the same thing, that is, the downloaded files start to differ at byte #4101<div><ul><li>The HTTPS version downloaded quite fast on my 5Mbps connection. The HTTP one is taking forever, quite literally; it's "stalled"</li><li>I've tried adding "Cache-Control: no-cache" and "Pragma: no-cache", but still getting the alternate file.</li></ul><div>tcptraceroute shows that the HTTP is most probably being cached; First using HTTP, then using HTTPS:</div></div><div><br></div><div><div>MacBook-Air:tmp $ tcptraceroute <a href="http://nodejs.org" target="_blank">nodejs.org</a> 80 </div><div>Selected device en0, address 192.168.1.107, port 57585 for outgoing packets</div><div>Tracing the path to <a href="http://nodejs.org" target="_blank">nodejs.org</a> (165.225.133.150) on TCP port 80 (http), 30 hops max</div><div> 1 192.168.1.1 4.144 ms 1.739 ms 1.139 ms</div><div> 2 <a href="http://lo10.cab2.hfa.nv.net.il" target="_blank">lo10.cab2.hfa.nv.net.il</a> (212.143.205.233) 15.141 ms 12.162 ms 11.659 ms</div><div> 3 <a href="http://core1-cab1-hfa.hfa.nv.net.il" target="_blank">core1-cab1-hfa.hfa.nv.net.il</a> (212.143.207.16) 15.204 ms 13.932 ms 12.857 ms</div><div> 4 <a href="http://gw2-0-2-0-1-core1.hfa.nv.net.il" target="_blank">gw2-0-2-0-1-core1.hfa.nv.net.il</a> (212.143.7.25) 11.599 ms 12.655 ms 16.048 ms</div><div> 5 165.225.133.150 [open] 157.406 ms 157.195 ms 168.028 ms</div><div><br></div><div>MacBook-Air:tmp $ tcptraceroute <a href="http://nodejs.org" target="_blank">nodejs.org</a> 443</div><div>Selected device en0, address 192.168.1.107, port 57586 for outgoing packets</div><div>Tracing the path to <a href="http://nodejs.org" target="_blank">nodejs.org</a> (165.225.133.150) on TCP port 443 (https), 30 hops max</div><div> 1 192.168.1.1 3.398 ms 1.755 ms 1.230 ms</div><div> 2 <a href="http://lo10.cab2.hfa.nv.net.il" target="_blank">lo10.cab2.hfa.nv.net.il</a> (212.143.205.233) 11.704 ms 16.318 ms 11.138 ms</div><div> 3 <a href="http://core1-cab1-hfa.hfa.nv.net.il" target="_blank">core1-cab1-hfa.hfa.nv.net.il</a> (212.143.207.16) 14.981 ms 13.580 ms 17.064 ms</div><div> 4 <a href="http://gw2-0-3-0-0-core1.hfa.nv.net.il" target="_blank">gw2-0-3-0-0-core1.hfa.nv.net.il</a> (212.143.7.53) 12.450 ms 14.393 ms 10.653 ms</div><div> 5 10.10.40.1 12.454 ms 18.778 ms 14.951 ms</div><div> 6 <a href="http://gw2-fra-0-3-0-3-200-gw2.hfa.nv.net.il" target="_blank">gw2-fra-0-3-0-3-200-gw2.hfa.nv.net.il</a> (212.143.12.12) 67.772 ms 68.099 ms 110.025 ms</div><div> 7 10.10.70.1 70.582 ms 76.711 ms 66.120 ms</div><div> 8 <a href="http://xe-4-3-2-302.fra23.ip4.gtt.net" target="_blank">xe-4-3-2-302.fra23.ip4.gtt.net</a> (77.67.94.5) 67.824 ms 66.694 ms 97.753 ms</div><div> 9 <a href="http://xe-1-2-3.was14.ip4.gtt.net" target="_blank">xe-1-2-3.was14.ip4.gtt.net</a> (89.149.180.198) 154.917 ms 167.244 ms 168.940 ms</div><div>10 <a href="http://internap-gw.ip4.gtt.net" target="_blank">internap-gw.ip4.gtt.net</a> (77.67.69.254) 164.903 ms 175.436 ms 158.257 ms</div><div>11 <a href="http://border10.pc2-bbnet2.wdc002.pnap.net" target="_blank">border10.pc2-bbnet2.wdc002.pnap.net</a> (216.52.127.73) 156.724 ms 153.793 ms 164.227 ms</div><div>12 <a href="http://joyent-3.border10.wdc002.pnap.net" target="_blank">joyent-3.border10.wdc002.pnap.net</a> (64.94.31.202) 166.082 ms 163.434 ms 163.415 ms</div><div>13 165.225.143.105 163.860 ms 169.177 ms 154.384 ms</div><div>14 165.225.143.15 178.280 ms 152.575 ms 159.958 ms</div><div>15 165.225.133.150 [open] 157.337 ms 162.811 ms 164.262 ms</div></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Sat, Mar 21, 2015 at 7:48 PM, E.S. Rosenberg <span dir="ltr"><<a href="mailto:esr+linux-il@g.jct.ac.il" target="_blank">esr+linux-il@g.jct.ac.il</a>></span> wrote:<br></span><div><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div>Depending on the version of windows and it's network environment you freshly installed rootkits could be likely, but that is OT here.<br><br></div>Note that different ISP in Israel is a fairly relative statement since there are basically just a few major players who own a bunch of the smaller ISPs and could have caching proxies on their international lines...<br></div><br></div>Did you traceroute the connection both from working and non-working settings?<br><br></div>Regards,<br></div>Eliyahu - אליהו<br></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">2015-03-21 8:30 GMT+02:00 Amos Shapira <span dir="ltr"><<a href="mailto:amos.shapira@gmail.com" target="_blank">amos.shapira@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Just speculating, but could it be that your ISP uses a caching transparent proxy (which would explain why it doesn't happen on SSL) and its cache got corrupted?<div>The "other ISP" case could be explained if it's actually upstream/downstream from your ISP, or they share a proxy cache for other reasons.</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On 21 March 2015 at 04:07, Roman Ovseitsev <span dir="ltr"><<a href="mailto:romovs@gmail.com" target="_blank">romovs@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div>Please forgive the slight off-topic, but I am experiencing a rather strange issue while downloading a certain file over HTTP.<br><br>Instead of getting node.js installer as expected from here <a href="http://nodejs.org/dist/v0.12.0/node-v0.12.0-x86.msi" target="_blank">http://nodejs.org/dist/v0.12.0/node-v0.12.0-x86.msi</a> I am receiving a completely different executable - an installer for Elcomsoft's Advanced EFS Password Recovery whatever that is.<br><br>Both files are exactly the same size but SHA sums obviously don't match.<br><br>SSL version of the link - <a href="https://nodejs.org/dist/v0.12.0/node-v0.12.0-x86.msi" target="_blank">https://nodejs.org/dist/v0.12.0/node-v0.12.0-x86.msi</a> works as expected. i.e. downloads the correct node.js installer.<br><br><br>I have verified this on three different machines running Fedora, CentOS, and Windows. None of these machines ever exchanged any files or used anything else but the default repos. In fact the windows machine is a 13 years old pc with a freshly installed OS. So presumably that dismisses any possibility of rootkits.<br><br>It doesn't seems to be due to my router or ISP either. I am getting the wrong executable on two of my neighbours' Wi-Fi networks and at least one of them seems to be using a different ISP.<br>However it doesn't happen on another Israeli nor a couple of US and UK servers I've tried so far.<br></div><div>I am not using any proxies either.<br><br></div><div><a href="http://nodejs.org" target="_blank">nodejs.org</a> domain on all of the above resolves to the same IP.<br><br><br></div><div>What's going on?<br>Could be that the ISPs are the culprit? <br><br></div><div>Considering that the application is relatively popular and I am the only one experiencing this issue it doesn't seem to be the case of <a href="http://nodejs.org" target="_blank">nodejs.org</a> server doing this on purpose (knowingly or not).</div></div>
<br></div></div>_______________________________________________<br>
Linux-il mailing list<br>
<a href="mailto:Linux-il@cs.huji.ac.il" target="_blank">Linux-il@cs.huji.ac.il</a><br>
<a href="http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il" target="_blank">http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il</a><br>
<br></blockquote></div><span><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div><div dir="ltr"><a href="http://au.linkedin.com/in/gliderflyer" target="_blank"><img src="https://static.licdn.com/scds/common/u/img/webpromo/btn_viewmy_160x25.png"></a><br></div></div>
</font></span></div>
<br>_______________________________________________<br>
Linux-il mailing list<br>
<a href="mailto:Linux-il@cs.huji.ac.il" target="_blank">Linux-il@cs.huji.ac.il</a><br>
<a href="http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il" target="_blank">http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Linux-il mailing list<br>
<a href="mailto:Linux-il@cs.huji.ac.il" target="_blank">Linux-il@cs.huji.ac.il</a><br>
<a href="http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il" target="_blank">http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il</a><br>
<br></blockquote></div></div></div><br></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><a href="http://au.linkedin.com/in/gliderflyer" target="_blank"><img src="https://static.licdn.com/scds/common/u/img/webpromo/btn_viewmy_160x25.png"></a><br></div></div>
</div>