-
Notifications
You must be signed in to change notification settings - Fork 317
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gin osx firewall issue #12
Comments
hm. I haven't run into this issue before. Are you still able to reproduce this? |
Yup, every time. I just run On Mon, Mar 3, 2014, at 05:35 PM, Jeremy Saenz wrote: hm. I haven't run into this issue before. Are you still able to — Reply to this email directly or [1]view it on GitHub. References |
Is this a gin-specific thing? Or Go's |
Well, as long as you're serving on 0.0.0.0 firewall comes up. If hoever On Mon, Mar 3, 2014, at 05:55 PM, Jeremy Saenz wrote: Is this a gin-specific thing? Or Go's net/http in general? In my — Reply to this email directly or [1]view it on GitHub. References |
ah okay. I know that martini can change the host via the HOST environment variable. maybe we should allow |
Same happened to me, because if your HOST environment variable is empty, the server is trying to bind to :3000, which needs permission from the firewall. The solution is to invoke gin like this: |
ah okay. Maybe we can set the host to localhost as the default instead. On Tue, Apr 15, 2014 at 11:47 AM, Tamás Demeter-Haludka <
|
Yeah that should work. On Tue, Apr 15, 2014, at 11:52 AM, Jeremy Saenz wrote: ah okay. Maybe we can set the host to localhost as the default instead. On Tue, Apr 15, 2014 at 11:47 AM, Tamás Demeter-Haludka < notifications@github.com> wrote:
— Reply to this email directly or [1]view it on GitHub. References |
Hi,
I started using
gin
today, but it keeps invoking OSX firewall each time the app binary is recompiled (in /gin-bin).I checked if proxy is trying to bind on 0.0.0.0, but thats not the case. So I don't know why is it invoking the firewall popups.
The text was updated successfully, but these errors were encountered: