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

Standardize default server-side FTE ports #12

Closed
kpdyer opened this issue Jun 4, 2013 · 0 comments
Closed

Standardize default server-side FTE ports #12

kpdyer opened this issue Jun 4, 2013 · 0 comments
Assignees
Labels
Milestone

Comments

@kpdyer
Copy link
Owner

kpdyer commented Jun 4, 2013

In the current release the FTE server binds to 127.0.0.1 on port 8080 and we forward all data to port 8081. This is probably not correct for most deployment. As a few examples of changes we want to make, we could make the following assumptions:

(1) FTE will bind to port 80.
(2) There will be a Tor bridge on the local machine running on port 9001, and we will forward all requests to this port.

However, should the FTE server reject a request to port 80 using a non-HTTP format? Or should the server just allow any supported format on any port?

@ghost ghost assigned kpdyer Jul 6, 2013
@kpdyer kpdyer closed this as completed in a8a71e4 Jul 11, 2013
kpdyer pushed a commit that referenced this issue Oct 14, 2013
…Wisc. FTE server, intersection-http and port 80. Will need to support more servers/formats in client-side configuration as requirements appear.
kpdyer pushed a commit that referenced this issue Oct 14, 2013
…Wisc. FTE server, intersection-http and port 80. Will need to support more servers/formats in client-side configuration as requirements appear.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant