Dmsgweb handle multiple tcp connections correctly #270
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Testing
serve hello world via tcp on port 8000
serve hello world via tcp on port 8002
(optional sanity check) test the tcp proxy
use ncat to access the tcp server via the proxy
then, stop the terminal running tcp-proxy.
Now, test proxying via
dmsg web srv
Those ports are now served over dmsg
COPY THE CLIENT PK
use dmsgweb we can put them back on other localhost ports so that we can access with netcat
Keep in mind that the logic for a simgle instance is different from multiple instances, so test these separately
one:
two:
Now attempt to access them via ncat (desired output shown below)