{"author":"Viktor Szakats","author_email":"commit@vsz.me","author_time":1741295619,"commit_time":1741395228,"committer":"Viktor Szakats","committer_email":"commit@vsz.me","hash":"abf80aae384319ef9b19ffbd0d69a1fbe7421f1f","message":"tests/server: fix to check against winsock2 error codes on Windows\n\nWindows's winsock2 returns socket errors via `WSAGetLastError()` and\nnot via `errno` like most systems out there. This was covered by\nswitching to the `SOCKERRNO` curl macro earlier. But, on Windows the\nreturned socket error codes have different values than the standard\nPOSIX errno values. Existing code was using the POSIX values for all\nthese checks. Meaning they never actually matched on Windows.\n\nThis patch defines a set of `SOCKERRNO` constants that map to the\ncorrect socket error values for Windows and other platforms.\n\nThe reverse issue exists in core curl code, which redefines POSIX errno\nvalues to winsock2 ones, breaking non-socket uses on Windows.\n\nCherry-picked from #15000\nFollow-up to adcfd4fb3e9be1de0e506728066bea2aaa53c394 #16553\nBug: https://github.com/curl/curl/pull/16553#issuecomment-2704679377\n\nCloses #16612\n","parents":["25f8486f269dfcd8e938ee7ed010a51b848fb36e"],"tree_hash":"47049b520caa698e5c485e85604160d54a54e169"}