<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div>Test url: rtmpdump -r
"rtmpt://ll2.workcast.net:80/vod1/mp4:Game300-LanguageXXX-Rec2_0_20110828151412811_1.mp4"
-W "http://c466722.workcast.net/flowplayer.commercial-3.2.5.swf" -p
"http://video.homelessworldcup.org/AuditoriumUsher.aspx?pak=6733772765126804&cpak=341
2165343567627" -o "VideoName.mp4" <br></div><div><br></div><div>i above test case server is sending the initial response broken in two tcp segments of length 145 and remaining. HTTP_Read consideres anything above 144 as complete response and parses it incorrectly which results in no client id being parsed which is necessary for further communication. attached patch tries to fix it by reading small packets in one go (handshake, commands, pings) and leave larger packets alone (audio, video). <br></div><div><br></div><div>@hyc <br></div><div>however even after applying the above fix i am still unable to download the video. it handshakes with server but server is rejecting second part of handshake. is it new type of rtmp handshake?<br></div></div></body></html>