Windows: initialize Winsock before proxy host validation (fix localhost config parse/init failure)

[Copilot]

The reported BSOD path points to WinDivert/kernel behavior, but this repository had a separate reproducible startup issue where hostname-based proxy config (notably localhost) could fail resolution and surface as invalid proxy state (e.g., :0). This PR narrows scope to that ProxyBridge-side initialization bug.

• Root cause

  • ProxyBridge_SetProxyConfig() validated proxy_ip via resolve_hostname() before guaranteeing Winsock was initialized.
  • Hostnames (vs raw IPv4 literals) therefore had a failure path during early config setup.

• Change

  • Initialize Winsock inside ProxyBridge_SetProxyConfig() before hostname validation.
  • Keep validation behavior unchanged; only make it deterministic for hostname inputs.
  • Clean up Winsock on both success and failure paths in this function.

• Resulting behavior

  • Proxy values like socks5://localhost:1080 and http://localhost:8080 now validate consistently during config setup, matching existing IP-literal behavior (127.0.0.1).

PROXYBRIDGE_API BOOL ProxyBridge_SetProxyConfig(...) {
    WSADATA wsa_data;
    if (WSAStartup(MAKEWORD(2, 2), &wsa_data) != 0) return FALSE;

    if (resolve_hostname(proxy_ip) == 0) {
        WSACleanup();
        return FALSE;
    }

    // existing config assignment logic...
    WSACleanup();
    return TRUE;
}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud