Skip to content
This repository has been archived by the owner on Jul 13, 2023. It is now read-only.

Use appropriate IP binding #1004

Closed
bbangert opened this issue Sep 8, 2017 · 0 comments
Closed

Use appropriate IP binding #1004

bbangert opened this issue Sep 8, 2017 · 0 comments
Assignees
@bbangert
Labels
bug p1
Milestone
2017Q2-3.1 Create...

Comments

@bbangert
Copy link
Member

bbangert commented Sep 8, 2017

The Rust PoC has a hardcoded IP binding to 127.0.0.1, it should use the appropriate passed in hostname for binding.
@bbangert bbangert self-assigned this Sep 8, 2017
bbangert added a commit that referenced this issue Sep 8, 2017
@bbangert
fix: use the config hostname to bind the websocket server
9351dfc 
This also cleans up the Rust with default rustfmt options.

Closes #1004
bbangert added a commit that referenced this issue Sep 8, 2017
@bbangert
fix: use config hostname for websocket server, apply rustfmt, and upd…
00a34ba 
…ate cargo deps

Closes #1004
bbangert added a commit that referenced this issue Sep 8, 2017
@bbangert
fix: use websocket hostname for server binding
2fef0fb 
Use rustfmt for Rust files and update Cargo deps.

Closes #1004
@bbangert bbangert mentioned this issue Sep 8, 2017
Merged
bbangert added a commit that referenced this issue Sep 8, 2017
@bbangert
feat: use config hostname for Rust websocket binding
30911ee 
Closes #1004
bbangert added a commit that referenced this issue Sep 8, 2017
@bbangert
feat: use config hostname for Rust websocket binding
2ef718f 
Closes #1004
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@bbangert bbangert

Labels
bug p1
Projects
None yet
Milestone
2017Q2-3.1 Create and implement a Rus...
Development

No branches or pull requests
1 participant
@bbangert