Release v2.0.9

What's Changed

• Check routes when checking for network changes by @samuong in #132
• Log final response status after authenticating by @samuong in #135

Full Changelog: v2.0.8...v2.0.9

Thanks to @smithjw for helping to test the networking changes!

Release v2.0.8

This fixes a build issue on Linux, see #130 for details.

Release v2.0.7

This fixes a build issue on macOS, see #128 for details.

For Linux and Windows users, this release should otherwise be identical to v2.0.6 and v2.0.5.

Release v2.0.6

Fix macOS build issue (#129)

Specifically, I've updated actions/setup-go to v5, and removed
maxim-lobanov/setup-xcode@v1. According to the comment, this was
required until the GitHub macOS runner was 11.x based, and according to
https://github.com/actions/runner-images it is now on macOS 14.

We also now upload CI build artifacts, which is useful for testing
purposes.

Release v2.0.5

This version sends the user's domain in the type 3 authenticate message, rather than the server's domain. This fixes a bug where Alpaca would fail to authenticate if the user was in a different domain to the proxy server.

Special thanks to @ziyiwang for reporting this bug (#126) as well as the two other bugs that were fixed in the previous release (#118 and #122), as well as for providing technical analysis and testing!

Release v2.0.4

What's Changed

• Update modules by @samuong in #121
• Close response body before moving on to next request/response by @samuong in #120
• Reimplement myIpAddress() to align with Chrome's algorithm by @samuong in #123

Full Changelog: v2.0.3...v2.0.4

Release v2.0.3

Write CONNECT response in a single call to Conn.Write() (#117)

This introduces a few changes from the previous version:

1. If we build an http.Response and call its Write() function, it will
   write the response line-by-line. This seems to be the cause of some
   flakiness with clients that start tunnel mode after the status line,
   rather than after the response header, as per RFC9110 9.3.6.

2. We only support HTTP 1.0 and 1.1. We no longer just blindly copy over
   the HTTP version from the client request.

3. The status code is still 200 but the status message has changed from
   "OK" to "Connection Established", in line with what other proxies are
   doing (I tested Squid, Martian and Zscaler). Clients ignore this
   anyway, going with the status code, so this shouldn't matter.

4. We no longer send a 'Connection: close' header with the response.
   This is redundant in a CONNECT request, and follows what other
   proxies (Squid, Martian and Zscaler) do.

Release v2.0.2

Fix IsInNet index out of bounds on invalid mask (#115)

If an invalid mask parameter is passed to IsInNet a
index out of bound panic will occur.

Release v2.0.1

Set Path and RawPath to "/" for https/wss URLs (#114)

Fixes #112

Release v2.0.0

Remove dodgy connection check (#108)

This behaviour worked well on some corporate networks, but breaks on
others. From now on, users who use a custom PAC file with a file:// URL
will need to do this check themselves, before returning a PROXY
directive.