<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 9/23/15 8:16 PM, gregrwm wrote:<br>
<blockquote
cite="mid:CAD+dB9BqML2wcJjawZCjG32+E67ZQkJw2Nnan9OkncfQpG_5Mw@mail.gmail.com"
type="cite">
<div dir="ltr">this is totally a headscratcher for me. my browser
fetches and displays the expected and reasonable pages for <a
moz-do-not-send="true" href="http://google.com">google.com</a>,
<a moz-do-not-send="true" href="http://www.kfai.org">www.kfai.org</a>,
and <a moz-do-not-send="true" href="http://yermande.org">yermande.org</a>.
and the first command below seems to successfully fetch <a
moz-do-not-send="true" href="http://google.com">google.com</a>'s
root page. however the second and third commands below get
surprising results from <a moz-do-not-send="true"
href="http://www.kfai.org">www.kfai.org</a> and <a
moz-do-not-send="true" href="http://yermande.org">yermande.org</a>.
any ideas what's happening?<br>
<br>
<span style="font-family:monospace,monospace"><font size="1">>$
exec 3<> /dev/tcp/<a moz-do-not-send="true"
href="http://google.com/80;echo">google.com/80;echo</a>
"GET /">&3;while read -r r;do echo
$r;done<&3|head -5</font></span><br>
</div>
</blockquote>
...<br>
<br>
Why not use curl or wget?<br>
<br>
If you want to use bash this way, try wireshark/tcpdump to see
exactly what's going down the wire.<br>
<br>
John<br>
<br>
</body>
</html>