That was the first hand experience that confirmed my suspicions of what those “free proxies” really are.
Calling: https://nsa.gov, headers = BOMBTHEMOSQUE -> 911
Calling: https://fbi.net
Calling: file:///bin/sh
Calling: file:///etc/passwd
Calling: http://127.0.0.1:80That's when I realized from the scrolling log messages that even residental ADSL was already under heavy probing from around the world.
I decided I didn't have the time or the stomach to try to deal with that at home, and there wasn't much I could do, so I disabled the logging.
That's a good point, another one is people using your proxy to attack other servers.
I find the proxy area to be interesting but something I'm unlikely to use for business, you are quoting some examples that made me laugh, and I'd certainly laugh if it happens to me, but I know I will remove the public access, if I were involved in business with this, the story would be different.
Thanks for sharing.
Or use it to get stuff on the internet that they don't want to get directly themselves. Once upon a time I accidentally enabled open proxying on the web server on my Linux box. This was before smart phones and tablets and such, when my Linux box was the only network client I had, and so I didn't have a NAT router. Just modem straight to Linux box.
One day I checked my Apache logs to see if my extremely low traffic web site had any visitors.
First impression: "What the hell is all this traffic? This is orders of magnitude more than I should have!".
Second impression: "Why the hell is someone trying to get horse_fucking.mov from my server?".
Third impression: "That didn't give a 404. Why is my server actually providing horse_fucking.mov?".
(No, the orders of magnitude extra traffic were not all people getting horse_fucking.mov. There was a whole plethora of bestiality titles, plus a lot of other porn that you would not want to fetch directly from your own IP address either out of embarrassment if you got caught or because it was almost certainly illegal).