Bug #2446

Starting next link immediately after a "busy" message

Added by drbits over 10 years ago. Updated over 10 years ago.

Status:NewStart date:09/24/2010
Priority:HighDue date:
Assignee:jiaz% Done:


Target version:040 - FarfarAway


After JD receives a "No slots available" or other "Server Busy" message, no attempt should be made to initiate a new download until after the server specified wait time (or 2 minutes if the server does not specify a wait time in the HTTP header).

Apparently, some plugins implement this, but most do not (the download proceeds to the next link). When there is no significant delay, this creates a mini-DoS attack.

This should be implemented at a higher level than the plugin. The plugin should return a Result Code of 503 when the server indicates it is busy.

Also available in: Atom PDF