Mathieu Schroeter

Results 88 comments of Mathieu Schroeter

Ok, it's seems that it's the normal behaviour.. it's lazy.. powerful but a bit problematic in my case

I'm working on Windows 8.1 and toolset v120_xp (Visual Studio 2013), boost 1.59 I start a node server on the same port that SimpleWebServer. Sometimes it's the node server which...

~~I must do that on Windows in order to have the exception:~~ ``` diff diff --git a/server_http.hpp b/server_http.hpp index 569a618..6917773 100644 --- a/server_http.hpp +++ b/server_http.hpp @@ -333,6 +333,7 @@ namespace...

Hello, Thanks for all Then yes, when I set the same address on node and on server_http then an exception is thrown. If node is binding on 0.0.0.0 then the...

Ok I've a case where it works as expected.. If server_http binds on 0.0.0.0, reuse_address is false and excluse_address is true, the exception is always thrown (tested with node on...

The working case: ``` c++ this->server->config.address = "0.0.0.0"; this->server->config.reuse_address = false; ``` (only valid with Windows) ``` diff diff --git a/server_http.hpp b/server_http.hpp index afb36c0..8d3cc48 100644 --- a/server_http.hpp +++ b/server_http.hpp @@...

The exception is always thrown (with my tests) if: 1. Server::config.reuse_address == false 2. SO_EXCLUSIVEADDRUSE == true 3. Server::config.address = "0.0.0.0" 4. The other server (node for example) binds on...

The `SO_EXCLUSIVEADDRUSE` flag smells just like a hack ``` c++ #define SO_EXCLUSIVEADDRUSE ((int)(~SO_REUSEADDR)) /* disallow local address reuse */ ``` Then I've tried with: ``` c++ int optval = 1;...