Might 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 ?
The name means it's likely to be blocked by the web filters it's meant to bypass.
Show HN: GoPee – Simple, Self-Hosted Web Proxy in Go
11–20 of 32 posts
Re: Show HN: GoPee – Simple, Self-Hosted Web Proxy in Go
#12Earlier 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.
@deftnerd Thanks for the appreciation! I understand the deficiencies are major ones, but I am gonna continue working on it.
good start,
nothing is ever perfect,
kudos to you for being open to the deficiencies and being happy fixing them
Re: Show HN: GoPee – Simple, Self-Hosted Web Proxy in Go
#13I wrote something like this a while back:
Re: Show HN: GoPee – Simple, Self-Hosted Web Proxy in Go
#14I wrote something like this a while back: https://github.com/aosmith/go-proxy
Goals are quite different however. Your project is more of a raw socket forwarder while OP's project attempts to be an anonymizing content proxy.
Re: Show HN: GoPee – Simple, Self-Hosted Web Proxy in Go
#15Another issue is that forms don't work.
doh! Issue logged. Will fix it. Thanks!
As someone that has worked on a similar project before -- I should caution you that allowing POST requests and such can open up a lot more potential for abuse (comment spammers, web-mail spam, etc) so you should add some rate limiting per-visitor-IP/target-domain or something similar before implementing this.
Re: Show HN: GoPee – Simple, Self-Hosted Web Proxy in Go
#16Earlier quoted context omitted.
doh! Issue logged. Will fix it. Thanks!
As someone that has worked on a similar project before -- I should caution you that allowing POST requests and such can open up a lot more potential for abuse (comment spammers, web-mail spam, etc) so you should add some rate limiting per-visitor-IP/target-domain or something similar before implementing this.
right.. thanks for the heads up ! But since it's a self-hosted solution, it would be very easy to just circumvent the rate-limiting and use it for malicious purpose ?
Re: Show HN: GoPee – Simple, Self-Hosted Web Proxy in Go
#17Earlier quoted context omitted.
As someone that has worked on a similar project before -- I should caution you that allowing POST requests and such can open up a lot more potential for abuse (comment spammers, web-mail spam, etc) so you should add some rate limiting per-visitor-IP/target-domain or something similar before implementing this.
right.. thanks for the heads up ! But since it's a self-hosted solution, it would be very easy to just circumvent the rate-limiting and use it for malicious purpose ?
Right, if your goal is privately hosted/accessible instances then it shouldn't be a problem. Just mentioning in case the goal is to offer it as a public service as it is at your main domain.
Re: Show HN: GoPee – Simple, Self-Hosted Web Proxy in Go
#18Nice! I wrote something similar in node.js a while back; so far it's gotten me banned from Heroku and nodejitsu :p
Re: Show HN: GoPee – Simple, Self-Hosted Web Proxy in Go
#19Might not be the best of names.
Has some pronunciation resemblance of "dog fart" in Chinese.
Re: Show HN: GoPee – Simple, Self-Hosted Web Proxy in Go
#20I get where "Go" comes from, obviously, but I'm confused about "Pee".