Port/Address re-use

[Frank-Friemel]

cpp-httplib/httplib.h

Line 2044 in d647f48

setsockopt(sock, SOL_SOCKET, SO_EXCLUSIVEADDRUSE,

Hi, I think there is a bug in the above line. This does not work. The return value is -1. I guess because you've previously enabled address re-use. Just applying SO_EXCLUSIVEADDRUSE (without SO_REUSEADDR) works.

I mean ... what is the purpose at all? In the Linux path you enable address/port re-usage. And in the Win32 path you try to disable it by acquiring the port exclusively? Currently it's enabled for both platforms, because SO_EXCLUSIVEADDRUSE fails. I stumbled over this because for my project this behaviour was kind of unexpected. My expectation was that a port can only be bound by one application/process/thread.

[yhirose]

@Frank-Friemel thank you for the report. I'll take a look at it when I have time.

[yhirose]

@Frank-Friemel sorry for the delay. As you mentioned, there is inconsistency between the Windows implementation and others (Linux and macOS). I actually prefer 'address/port re-usage' over 'exclusive address usage'. As for Windows, it seems I misunderstood the WinSock spec. (#506 (comment))

So in order to make all the platform behaviors consistent, I am actually removing SO_EXCLUSIVEADDRUSE from the Windows implementation.

If you would like to have 'exclusive address usage', you can set the socket option to SO_EXCLUSIVEADDRUSE with Server::set_socket_options.