Something is wrong when you accept new connection. This leads to problems when you want enable jumbo frames in your network. Here is how to reproduce it on localhost, but the real environment would be between two machines - and the behaviour is the same.
Simulate jumbo frame support on localhost:
$ sudo ip link set mtu 2500 dev lo
Hi
Something is wrong when you accept new connection. This leads to problems when you want enable jumbo frames in your network. Here is how to reproduce it on localhost, but the real environment would be between two machines - and the behaviour is the same.
Simulate jumbo frame support on localhost:
$ sudo ip link set mtu 2500 dev lo
run ws server and connect 'curl http://localhost:9002:
run asio echo server and connect 'telnet localhost 8888'
You can see that for websocket connection wrong MSS is calculated. In attachement you can see two directories:
asio_async_server asio_async_server conatins asio server from boost asio examples with MTU/MSS debugging infomation. Building:
Running on i.e. port 8888
./asio_server 8888
Connecting - from another consoletelnet localhost 8888
wss wss server conatins websocketpp server based on example code from your repository. Server is running on port 9002 Building
Running
./wss_server
Connecting - from another consolecurl http://localhost:9002
Br, krzysiek6d bug.zip