Slashdot.org blocking Winnersh proxy server

melevittfl · 21-01-2005, 15:30

Hi,
The website www.slashdot.org is blocking access from 62.253.96.40, the IP address of the Winnersh proxy servers.

They say to e-mail them with the IP address in the subject line, which I've done, and explained that it is a proxy server.

I got a response from Robert Rozeboom <samzenpus [ at ] slashdot.org>:
"This IP was used to crapflood us over the Holiday weekend, if you can have
the person/s in charge of your Ip contact me I can try to get you off the
banned list."

So, can one of the NTL techs responsible for this proxy contact him? Or pass this along to whomever is appropriate?

Thanks.

Chris W · 21-01-2005, 16:03

Slashdot seem to block various ntl proxies quite often.... i wonder why they can't code their website properly to detect real ips instead of proxy server ips

i will pass the details on to the appropriate people.

MB

IanUK · 21-01-2005, 16:14

Any chance of getting Ebuyer fixed with the Poplar proxies as mentioned here a few days ago, it still doesn't work

http://www.cableforum.co.uk/board/sh...ad.php?t=22879

melevittfl · 21-01-2005, 16:24

Quote:

Originally Posted by monkeybreath

i will pass the details on to the appropriate people.
MB

Fantastic. Thanks.

Mark

Gareth · 21-01-2005, 17:00

Quote:

Originally Posted by monkeybreath

Slashdot seem to block various ntl proxies quite often.... i wonder why they can't code their website properly to detect real ips instead of proxy server ips

<snip>

Yep, but I wonder how'd you'd be able to do that.... unless you had a list of proxies that you dynamically refreshed and compared IPs against that list...? I'm sure there's a much better/effective way - anybody care to enlighten me?

Toto · 21-01-2005, 17:03

Slashdot.................LOL, they still can't configure their web log servers to record HTTP_X_FORWARDED_FOR and/or HTTP_CLIENT_IP, which is the variable you need to capture client IP addresses over proxy servers.

You would think with the pool of knowledge those guys have got, they could do something so basic

BTW, those guys who have those nice IP signature scripts running, you may also want to add those variables too, honestly, I don't need reminding that I am on an ntl cache.

melevittfl · 22-01-2005, 05:52

I suspect they can find the client IP, but they assume a proxy server with a large number of users, some of whom are misbehaving, may be an open proxy.

So, being unable to distinguish between an open proxy and a transparent proxy of a large ISP, they take the easy route.

Toto · 22-01-2005, 11:45

Quote:

Originally Posted by melevittfl

I suspect they can find the client IP, but they assume a proxy server with a large number of users, some of whom are misbehaving, may be an open proxy.

So, being unable to distinguish between an open proxy and a transparent proxy of a large ISP, they take the easy route.

Agreed.

Their loss though, and not a very good advert for their so-called expertise

Richard M · 22-01-2005, 12:25

Quote:

Originally Posted by Toto

Slashdot.................LOL, they still can't configure their web log servers to record HTTP_X_FORWARDED_FOR and/or HTTP_CLIENT_IP, which is the variable you need to capture client IP addresses over proxy servers.

You would think with the pool of knowledge those guys have got, they could do something so basic

BTW, those guys who have those nice IP signature scripts running, you may also want to add those variables too, honestly, I don't need reminding that I am on an ntl cache.

I find it quite amusing that they inform me that my ISP is phpfuture.net because I have a static IP with some DNS going on.