<div dir="ltr"><div>Of course wireshark has a great UI and is probably the recommended tool for much of this kind of work.<br>I find the technique used to define filters a bit obscure but that's probably a familiarity issue as much as anything else.<br>
<br>I tend to use tcpdump for this kind if thing.<br><br>sudo tcpdump -s1564 -w - port 80 | strings<br>
</div><div>sudo tcpdmup -s1500 -X -vv port 80<br><br><br><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, May 1, 2014 at 10:35 PM, David L. Anselmi <span dir="ltr"><<a href="mailto:anselmi@anselmi.us" target="_blank">anselmi@anselmi.us</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">Christopher Cross wrote:<br>
> I have the same script on two different machines.<br>
<br>
</div>There's a .curlrc that might give different options.<br>
<br>
I would look at wireshark to see what's different.<br>
<br>
Dave<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
clue mailing list: <a href="mailto:clue@cluedenver.org">clue@cluedenver.org</a><br>
For information, account preferences, or to unsubscribe see:<br>
<a href="http://cluedenver.org/mailman/listinfo/clue" target="_blank">http://cluedenver.org/mailman/listinfo/clue</a><br>
</div></div></blockquote></div><br></div>