Security Code - always wrong?
-
Hey guys! Iam trying to download a file and everytime I try to download any torrent it says "Too Many requests" and Ok, I get it, it's the system trying to verify if iam not a machine. But everytime I enter the code, it says that's wrong, I mean, every single time! Its been a few days since iam trying and it does not happen when I browse the forum, only at the torrent search.
Can you guys help?
Best regards,
-
Usually that happens if you open multiple pages one after the other before entering the security code. Each new page call generates a new code, but if you haven't refreshed the page, you'll see still the old picture. Another issue can result from an old security code picture being in the browser cache.
First thing to try:
Refresh / reload the page you see with the security code request and wait a few seconds until a new security code picture is displayed. Then enter that new security code. If you have other pages open asking a code, just refresh the page, it should show the page you wanted to go.
If that doesn't help:
Clear the browser cache and cookies. Try again as above.
If that doesn't help:
Try another browser
-
Thanks Uwe, I was using Firefox, then tried with Internet Explorer and workid! Now iam abble to download on both. This could mean that when they implemented the "Security Code" it was in poorly way. It can become an exploit 'cos the code is not checked on every connection but in a user database.
Let's think that's will not happen in any time soon.
Best Regards,
-
Hi Laibach,
actually, this sort of failures is not because of "bad programming", or "bad implements, but because not all browser behave like they should, when it comes to session-ids and temporary content. Even if you tell FireFox, NOT to save any cache-items, it still saves the temporary parts and displays the "old" security code image with the wrong session-id, which is only valid for one time only. If you do any other request, before the input of the right code, the security code isn't valid any more and therefore a new security code is built. The "normal" function for the session would be deleting the session-id and cache-items and requesting the hole content from the server again, but due to performance reasons, FireFox isn't requesting a new session-id with the download of the new security code image and that's the reason, why these failures happen.
… and no (!!!), there is no possibilty that this failure may be used for an exploit, because the server builts a new session-id and a new security image every time, untill you put in the right code. Any other code is blocked during this security procedure.