View Single Post
  #6  
Old 06.06.2011, 21:59
bboard
Guest
 
Posts: n/a
Default

Despite the update for Bug #3317 today, the error is still not handled correctly neither for free user (404 which results in a permanent 'file not found' marking in JD), nor for premium users (still results in a plugin defect).

I assume ul.to changed their site again after #3317 was fixed. You can just use the urls above to test.


The issue with these 2 files when downloading with a premium account is that instead of doing a 'POST /dl/<downloadtoken> HTTP/1.1', I can see JD doing a 'GET /file/<fileid>/dl/<downloadtoken> HTTP/1.1'. In the browser, after the 'POST /dl/downloadtoken HTTP/1.1', I can see the following part in the html content:

Code:
	<div style="text-align:center;padding:30px 0px;">
		<p style="margin:10px 0px;">
			Aus technischen Gründen ist ein Download momentan nicht möglich.		</p>
		<p style="margin:10px 0px;">
			In <b id="tout">16</b> Sekunden wird ein erneuter Versuch gestartet&hellip;
		</p>
			</div>

seems like this error message is always in german btw.
Reply With Quote