Issue #1088 new

SO_REUSEADDR should not be used on windows

Anonymous created an issue

The standard idiom of creating a socket with SO_REUSEADDR before binding, should not be done on windows. The meaning of this socket option is quite different on windows. On windows, the default behaviour is as though SO_REUSEADDR had been specified on unix. If this flag is specified, it is possible to bind to a port that is actually in use. See for example this discussion from twisted:

And this documentaton on the flag and its windows specific colleagues:

Reported by

Comments (1)

  1. Log in to comment