Would a blurb like this in the report section work?<br><br><div style="margin-left: 40px;">Note: The following hosts resolved to multiple IP addresses. Results for these hosts may need to be verified for consistency.<br>
<a href="http://a0.twimg.com">a0.twimg.com</a> 209.170.97.173, 209.170.97.183<br> <a href="http://a1.twimg.com">a1.twimg.com</a> 204.160.114.126, 204.160.103.126<br> <a href="http://a2.twimg.com">a2.twimg.com</a> 209.170.97.192, 209.170.97.189<br>
<a href="http://a3.twimg.com">a3.twimg.com</a> 204.160.103.126, 204.160.114.126<br> <a href="http://twitter.com">twitter.com</a> 168.143.162.36, 128.242.240.212, 128.242.245.116<br></div><br>From a couple of runs through this url, it seems that the hosts in the 209.170.* range seem to work, but the hosts in the 204.160.* range do not. YMMV. <br>
<br>Code v 0.03 attached.<br><br>On Wed, Nov 10, 2010 at 7:04 PM, Whizz Mo <<a href="mailto:https@whizzmo.com">https@whizzmo.com</a>> wrote:<br>><br>> Yes, the setup that Twitter runs is beyond my script's recognition abilities. I suppose that I could put in IP range matching logic to check if the hostname resolves to something in Amazon's cloud, but I don't really want to maintain an IP range list over time. I'm hoping that the current output (with the partial string display) is enough to point people in the right direction. <br>
><br>> On Wed, Nov 10, 2010 at 6:23 PM, Seth David Schoen <<a href="mailto:schoen@eff.org">schoen@eff.org</a>> wrote:<br>>><br>>> Whizz Mo writes:<br>>><br>>> > Here are 80 bytes from both strings, starting at offset 1732:<br>
>> > http: ref="<br>>> > <a href="http://a1.twimg.com/a/1289433550/images/twitter_57.png">http://a1.twimg.com/a/1289433550/images/twitter_57.png</a>" rel="apple-touch-ic<br>
>> > https: ref="<br>>> > <a href="https://s3.amazonaws.com/twitter_production/a/1289433550/images/twitter_57">https://s3.amazonaws.com/twitter_production/a/1289433550/images/twitter_57</a>.<br>
>> ><br>>> > Note that the starting byte of each listed string is 10 chars before the<br>>> > variance occurs. For sites with rotating ad banners, this may be an<br>>> > issue.<br>>><br>
>> This particular discrepancy is actually an HTTP/HTTPS issue; these<br>>> hosts are both Amazon S3 but the latter is the HTTPS name for the<br>>> same resource. For this particular image -- unlike many others --<br>
>> Twitter realized that it should generate the HTTPS name for the<br>>> image resource in order to avoid a mixed-content warning.<br>>><br>>> --<br>>> Seth Schoen<br>>> Senior Staff Technologist <a href="mailto:schoen@eff.org">schoen@eff.org</a><br>
>> Electronic Frontier Foundation <a href="https://www.eff.org/">https://www.eff.org/</a><br>>> 454 Shotwell Street, San Francisco, CA 94110 +1 415 436 9333 x107<br>><br>><br><br>