in reply to Re: Detect Open Proxies
in thread Detect Open Proxies

Thanks for visitng the node i wrote

i didn't mean any harm by this subject , i could take proxies manually one by one put them in my browser and test them therefore you can consider it as automating a job

i don't need to test them for anything bad, i need them for a checking props , like in IRC chat if you used it

my node is allmost harmless and if you see its not good enough to be here , ask for deletion ... i just want one reason to take it as a bad thing ???

at last Sorry for my weak english , if there's anything you can't understand in my words i will try my best explaining it to you

Replies are listed 'Best First'.
Re^3: Detect Open Proxies
by merlyn (Sage) on Dec 15, 2005 at 01:43 UTC
    at last Sorry for my weak english , if there's anything you can't understand in my words i will try my best explaining it to you
    Well, you could start by explaining why you need to test weak proxies. That'd help me. If it's simply "I need to remove them" ok, But if it's "I need to expoit them" then I need a chance to object.

    -- Randal L. Schwartz, Perl hacker
    Be sure to read my standard disclaimer if this is a reply.

[reply]

      Hello

      well , i'm not testing for open ports , it's just a test for open proxies .

      plus as i told you it's for chat needs , when the chat works in server side with out client, you can't give out a good ban ...

      i could ban using REMOTE_ADDR , HTTP_X_FORWARDED_FOR ...

      but if some one has the ability to change his proxy and login again , there will be no benefit from banning him

      if you have a good way to do this without searching for open proxies .... i will be so helpfull for me if you add it over here

[reply]
[reply]

In Section Seekers of Perl Wisdom