Releases: pires/go-proxyproto
Releases · pires/go-proxyproto
v0.3.2
v0.3.1
v0.3.0
This release is only possible with the amazing work by @emersion to whom I want to say thank you very much!
Breaking changes
- Rely on
net.Addr
, which allows to represent any network address, instead of using an IP and a port (#46)- New helpers (
header.{TCPAddrs(),UDPAddrs(),UnixAddrs(),IPs(),Ports()}
) allows to easily extract data fromnet.Addr
attributes. - The
header.{Local,Remote}Addr
helpers have been removed in favor or accessorsheader.{Source,Destination}Addr
.
- New helpers (
TLV.Length
has been removed, in favor of usinglen(TLV.Value)
instead (#42)
Improvements
v0.2.0
Bug-fixes
- Fix protocol header for unknown protocol (#27)
- Documented a problem with AWS NLB when your server is configured to speak first "AWS Network Load Balancer (NLB) does not push the PPV2 header until the client starts sending the data. This is a problem if your server speaks first. e.g. SMTP, FTP, SSH etc." (#25)
Improvements
- Enable easy Header creation from a source and destination
net.Addr
. If thenet.Addr
cannot be represented, the transport information is left unspecified (#31) - Avoid buffer growing allocation by setting a size of 108 as per RFC "a 108-byte buffer is always enough to store all the line and a trailing zero for string processing" (#27)
- Client example (#37)
- Many code improvements, such as carry package name in errors (a la Go) and stop exporting values that shouldn't be exported (#30 #32 #33)
Thanks
v0.1.3
0.1.2
Bug-fixes
-
Surface error when parsing header (#21)
Before this fix, all errors would be masked as
ErrNoProxyProtocol
, including errors liketls: first record does not look like a TLS handshake
. Mad props to @igorwwwwwwwwwwwwwwwwwwww for finding this and providing a patch.