common they just should act a bit more relaxed on this. Just because a normal HTTP protocol feeature (as this CONNECT) is used on a server wouldn't mean it's a malicious behavior. Thats just silly and ignorant.
If that server doesn't want to to be used (and yes in this case by a wrong mean) just don't put it online. It's just silly to scream for action on this! It's like walking out and arguing that the air is a bit cold today! If so, just don't walk out!
Anyway, if they don't have the details to this, then sorry, they just show "45.#.#.195" as IP.
"We have to forward complaints as received, BitNinja is lower on the
priority list as their complaints are vague at best, but we do have to forward
all complaints. At this time we would consider this one closed."
Ahh perfect. Im glad they see it the same as I. Everything else would just be too funny. Because all that happened is
1. open a tcp/ip connection to that IP:80 2. sending "CONNECT <other ip>:80"
The second a test if that server supports this feature. There is nothing to worry about. IF that server does not want this, simplya reply with a 500 and it's OK.
Comments
Thats all I can see here.
Why this should be a problem is however very questionable.
If that server doesn't want to to be used (and yes in this case by a wrong mean) just don't put it online.
It's just silly to scream for action on this! It's like walking out and arguing that the air is a bit cold today! If so, just don't walk out!
Anyway, if they don't have the details to this, then sorry, they just show "45.#.#.195" as IP.
1. open a tcp/ip connection to that IP:80
2. sending "CONNECT <other ip>:80"
The second a test if that server supports this feature.
There is nothing to worry about. IF that server does not want this, simplya reply with a 500 and it's OK.