<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div><br>On Jan 11, 2008, at 10:14 PM, Luigi Auriemma wrote:</div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000">Now talking about you, Marcello, the problem you had is just with "your"<br>same computer/network, probably you have a firewall or something else (a<br>"condition" as you define it) that simply makes your ports to appear<br>filtered/timedout and so Quicktime gives up.<br></font></div></blockquote><div><br></div><div>Yeah, you are right. Protocol switching was disabled in my Quicktime</div><div>preferences. Sorry about that.. I should have checked before writing</div><div>inaccurate statements here.</div><div><br class="webkit-block-placeholder"></div><div>By the way, even with "Transport setup" -> "Automatic", the software</div><div>doesn't crash nor loops after reading the HTTP payload, but I really</div><div>don't know why.. It merely sits there, saying "Swiching transports".</div><div><br class="webkit-block-placeholder"></div><div>Attached a full pcap dump of the session and QuickTime.app's version</div><div>plist.</div><div><br class="webkit-block-placeholder"></div><div>Have fun! :)</div><div><br class="webkit-block-placeholder"></div><div>Marcello</div><div><br class="webkit-block-placeholder"></div><div></div></div></body></html>