FRD stop retry next proxy after failure

shawn8888

FRD stop retry next proxy after failure
March 31, 2011 03:50AM

Registered: 15 years ago
Posts: 166

I have plenty of good proxies in the list, and sometimes when a megaupload link failed with an error "File name not found", it stops retrying the next proxy in the list. So I have to manually hit Resume button to continue the job, which is quite annoying.

I am not sure if this is a plugin issue or a generally problem. Please look into it.

Thanks a lot!

Edited 2 time(s). Last edit at 03/31/2011 03:51AM by shawn8888.

Reply Quote

Attachments:
open | download - frd.png (14.9 KB)

ntoskrnl

Re: FRD stop retry next proxy after failure
March 31, 2011 06:21AM

Admin
Registered: 15 years ago
Posts: 2,094

It's a strange problem with the proxy, because that means FRD receives some kind of a web page, but not the correct MU one and hence can't find the file name. We can't really change anything to accommodate for this as it would change things for broken plugins.

You can check app.log after such an error to see what it received.

Edited 1 time(s). Last edit at 03/31/2011 06:22AM by ntoskrnl.

Reply Quote

Vity

Re: FRD stop retry next proxy after failure
March 31, 2011 06:25AM

Admin
Registered: 20 years ago
Posts: 2,425

Only transparent web proxies are (and can be) supported.

-------------------------------------

Edited 1 time(s). Last edit at 03/31/2011 06:28AM by Vity.

Reply Quote

shawn8888

Re: FRD stop retry next proxy after failure
March 31, 2011 07:20PM

Registered: 15 years ago
Posts: 166

Vity Wrote:
-------------------------------------------------------
> Only transparent web proxies are (and can be)
> supported.

I agree. But I think RFD should at least try 2-3 different proxies in the list before stop trying.

ntoskrnl Wrote:
-------------------------------------------------------
> It's a strange problem with the proxy, because
> that means FRD receives some kind of a web page,
> but not the correct MU one and hence can't find
> the file name. We can't really change anything to
> accommodate for this as it would change things for
> broken plugins.
>
> You can check app.log after such an error to see
> what it received.

Why not?
If one proxy doesn't return the proper web page, FRD should try the next proxy. ONLY if the proxy gets a clear message saying "the file is deleted" or something like that, or all proxies in the list are not working, should RFD stop trying in my opinion.

Edited 1 time(s). Last edit at 03/31/2011 07:21PM by shawn8888.

Reply Quote

shawn8888

Re: FRD stop retry next proxy after failure
March 31, 2011 11:18PM

Registered: 15 years ago
Posts: 166

here is the app.log.
I can not see the url links in the log by the way.

Reply Quote

Attachments:
open | download - applog.rar (64.7 KB)

ntoskrnl

Re: FRD stop retry next proxy after failure
April 02, 2011 08:45AM

Admin
Registered: 15 years ago
Posts: 2,094

The FileSonic error says "Attention! We have detected some suspicious behaviour coming from your IP address (222.162.105.110) and have been temporarily blocked."

The whole MegaUpload page that FRD received was this:

<!-- DW6 -->
<head>
<!-- Copyright 2005 Macromedia, Inc. All rights reserved. -->
<title></title></head>

And how do you think we should determine whether an unrecognized page that was returned is the real MegaUpload page which has just been changed a bit or a fake page returned by a messed up proxy?

Reply Quote

shawn8888

Re: FRD stop retry next proxy after failure
April 08, 2011 08:11PM

Registered: 15 years ago
Posts: 166

Sorry ntoskrnl, I just saw your reply.
Here are my thoughts:

When should FRD shop trying and show the red error message? If EIGHT of the following conditions apply
a. When the host sends a CLEAR message that the file on the page is deleted or not exist
b. When more than a maximum attempts is reached using different proxy if possible. This retry count should be able to set by the user in the options screen.

Some hosts may block a proxy for a weird reason, like "suspicious behaviour" message you mentioned above, and if you try again, it may work! It may also happen to you even without using a proxy. But FRD really should not give up so quickly when you have a bunch of proxies in the list and it is painful that you have to resume it manually!

Edited 4 time(s). Last edit at 04/08/2011 08:17PM by shawn8888.

Reply Quote

ntoskrnl

Re: FRD stop retry next proxy after failure
April 09, 2011 08:21AM

Admin
Registered: 15 years ago
Posts: 2,094

The issue with a) is that sometimes hosts change their page a bit which makes FRD unable to recognize some information on the page. In that case we don't want to bombard the host with useless requests. Also, we want users to see a clear error message so they can report the problem specifically.

We strive to support all possible error messages (including "suspicious behavior" ones), but as some of them are very rare, we don't even know of their existence.

Reply Quote

shawn8888

Re: FRD stop retry next proxy after failure
April 09, 2011 05:12PM

Registered: 15 years ago
Posts: 166

If you need the user to see "all possible error messages", why only show “File name not found” instead of the real error message "suspicious behavior ..."? Also, why is that message so important if all the use can do is just clicking resume button and retry?

If FRD only retry about 10 times (not infinity!) , how could it "bombard the host"? Besides, I believe the error doesn't happen that often, and even it happens, most hosts are not that vulnerable as you think they are.

Reply Quote

Vity

Re: FRD stop retry next proxy after failure
April 09, 2011 05:26PM

Admin
Registered: 20 years ago
Posts: 2,425

10 * 2 mil users

-------------------------------------

Reply Quote