You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: