Nice! I wrote something similar in node.js a while back; so far it's gotten me banned from Heroku and nodejitsu :p
Show HN: GoPee – Simple, Self-Hosted Web Proxy in Go
21–30 of 32 posts
Re: Show HN: GoPee – Simple, Self-Hosted Web Proxy in Go
#22Re: Show HN: GoPee – Simple, Self-Hosted Web Proxy in Go
#23I think a slightly more practical approach would be to make an easily self-hosted web proxy with an accompanying Google Chrome (or other) extension that can rewrite all network requests.
Re: Show HN: GoPee – Simple, Self-Hosted Web Proxy in Go
#24Nice! I wrote something similar in node.js a while back; so far it's gotten me banned from Heroku and nodejitsu :p
Why did it got you banned on those services??
On Nodejitsu, someone tweeted links to porn that went through my proxy, and they disabled the site thinking that I was using their service to host porn. The CEO told me that they'd turn it back on if I added user accounts and a way to ban users. But at that point, I had a newborn son and was in no mood to put a bunch of development work into making my anonymous proxy not-so-anonymous.
So, right now, it's still offline. The source is at https://github.com/nfriedly/node-unblocker if anyone's interested.
Re: Show HN: GoPee – Simple, Self-Hosted Web Proxy in Go
#25I think a slightly more practical approach would be to make an easily self-hosted web proxy with an accompanying Google Chrome (or other) extension that can rewrite all network requests.
[deleted]
Glype [1] is an example of web proxy that provides rewriting and customizable plugins to improve compatibility with complex web apps. Not free software but comes with source code (PHP).
Re: Show HN: GoPee – Simple, Self-Hosted Web Proxy in Go
#26I get where "Go" comes from, obviously, but I'm confused about "Pee".
Re: Show HN: GoPee – Simple, Self-Hosted Web Proxy in Go
#27I get where "Go" comes from, obviously, but I'm confused about "Pee".
Re: Show HN: GoPee – Simple, Self-Hosted Web Proxy in Go
#28Earlier quoted context omitted.
Great start. Your two known deficiencies are pretty big right now: * Doesn't support anything which requires sessions / cookies / logging in, yet * Most AJAX requests don't work since the URLs are not rewritten Don't stop working on it! This is a pretty great project.
Other issues: * It's leaking a lot of information (Google Analytics and a few other domains are being connected to directly instead of going through proxy). This is probably the biggest thing to fix. Offering a "strip all scripts" option may help. * Useragent is set to Go's default. Forwarding the user's user-agent or better yet, a stock browser useragent (Firefox or something) may be better
Re: Show HN: GoPee – Simple, Self-Hosted Web Proxy in Go
#29Might not be the best of names.
@mkr-hn I understand. But, just check the site title if you haven't already. Maybe that would help see it from a different angle ?
But the single most enjoyable experience I've ever had peeing was at Martin's West in Redwood City.
They have an old-fashioned long tray shared urinal like we had in kindergarten, but thankfully I was there early and had the whole thing to myself. And they had just filled the entire tray with crushed ice!
If your aim is good, you can make any pattern you want. I tried for the Mandelbrot but only got a few spirals going. But man, was it fun!
What did you say your open source project does again?
Re: Show HN: GoPee – Simple, Self-Hosted Web Proxy in Go
#30Earlier quoted context omitted.
Great start. Your two known deficiencies are pretty big right now: * Doesn't support anything which requires sessions / cookies / logging in, yet * Most AJAX requests don't work since the URLs are not rewritten Don't stop working on it! This is a pretty great project.
Other issues: * It's leaking a lot of information (Google Analytics and a few other domains are being connected to directly instead of going through proxy). This is probably the biggest thing to fix. Offering a "strip all scripts" option may help. * Useragent is set to Go's default. Forwarding the user's user-agent or better yet, a stock browser useragent (Firefox or something) may be better
SOME effort could be made to rewrite URLs found inside of Javascript but that might be a terrible idea in practice.