Skip to content
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

web-server bind interface issue #430

Closed
bonesoul opened this issue Sep 8, 2014 · 3 comments · Fixed by #433
Closed

web-server bind interface issue #430

bonesoul opened this issue Sep 8, 2014 · 3 comments · Fixed by #433
Milestone

Comments

@bonesoul
Copy link
Owner

bonesoul commented Sep 8, 2014

Interesting. Set it with artbatista.com does not work, set it to www.artbatista.com it works.
Can't you just make this so that it will allow connections to an ip number, without regard as to where
the original http requested pointed to?
That way when I ask my browser to go to "artbatista.com", the router will sent to 192.168.1.109, and all > I have to set in the config file is bind to 192.168.1.109

discussion: https://bitcointalk.org/index.php?topic=604476.msg8724782#msg8724782

our web-server should be able to listen on ip and any domain bound to it.

@bonesoul bonesoul added this to the 0.1.6 - next minor release milestone Sep 8, 2014
@bonesoul
Copy link
Owner Author

bonesoul commented Sep 8, 2014

@bonesoul
Copy link
Owner Author

bonesoul commented Sep 8, 2014

possible fix: 406193c

@bonesoul
Copy link
Owner Author

bonesoul commented Sep 8, 2014

reported that the fix is working; https://bitcointalk.org/index.php?topic=604476.msg8732983#msg8732983

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant