<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div>Stef wrote:<br>>Seriously, cmon, it's not big deal! What's a few characters or a bit of pre-parsing going to cost you?</div><div>and who said it's big deal. i can certainly define required options. however it was certainly unexpected behavior even after using --swfAge 0. <br></div><div><br></div><div>Howard Chu wrote:</div><div>>We should've dropped Windows support. At least Linux users tend to know how to <br>>tinker on their own, instead of whining that it's not Fully AutoMagical.</div><div>the issue would have been same for non whining linux users. doesn't auto hashing benefits the linux users in same way.<br></div><div><br></div><div>Howard Chu wrote:</div><div>> This was done to accomodate ABC Australia's iView, which uses the
same SWF file but with a randomly generated hash in the middle of the
URL on each session. Looks like a different solution is needed.</div><div>wouldn't it be better to check if the url contains iView swf hosting domain and then apply hlen and full url comparison in other cases.</div><div>i would have written the patch but i am not aware of their swf hosting domains. i tried few free proxies and vpn's but it didn't worked.</div><br><div>just for reference see last few posts here for original problem:<br></div><div>http://stream-recorder.com/forum/recording-kelby-training-www-kelbytraining-com-videos-t8873p8.html</div></div></body></html>