Re^3: Detect Open Proxies

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.

Comment on Re^3: Detect Open Proxies

Replies are listed 'Best First'.
Re^4: Detect Open Proxies by ahmad (Hermit) on Dec 15, 2005 at 13:39 UTC
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]
Re^5: Detect Open Proxies by merlyn (Sage) on Dec 15, 2005 at 17:01 UTC
There are hundreds of open proxies. You'll never be able to block them all. Perhaps you should rethink your authentication strategies. -- Randal L. Schwartz, Perl hacker Be sure to read my standard disclaimer if this is a reply.	[reply]
Re^6: Detect Open Proxies by ahmad (Hermit) on Dec 15, 2005 at 18:47 UTC
therefore i'm not going to block them , i'm thinking to check on login if the user is using open proxy , he'll not be able to login , if not then he's welcome whatever the authentication was , it will stay the same ... as i think blocking users with open proxies is the best way	[reply]