{"push_id":1201396149,"size":2,"distinct_size":2,"ref":"refs/heads/non_blocking_remote_addr","head":"c264d774d2ac86c2802da7daa57ce015f53e2010","before":"ec9b7b5e1146e7b95397a7a82fa3884e6055025b","commits":[{"sha":"07ded959fafbb95483951986757a93486ab4cc52","author":{"name":"Hector Rivas Gandara","email":"7b7e5985d0d5e042df62f31a43aa47b3c2b7c938@gmail.com"},"message":"Add optional timeout to get PROXY header\n\nThe library user can define a maximum time to wait\nfor the PROXY protocol header, before failing out to\nnormal connection.\n\nWe can assume that a proxy in front of the service will\nsend the PROXY header immediatelly.\n\nThis solves the issue of clients getting block when\ngetting the RemoteAddr() for an incoming connection that\ndoes not send any data. That is the case of http.Serve on\ngo < 1.6 as described in https://github.com/armon/go-proxyproto/issues/1","distinct":true,"url":"https://api.github.com/repos/keymon/go-proxyproto/commits/07ded959fafbb95483951986757a93486ab4cc52"},{"sha":"c264d774d2ac86c2802da7daa57ce015f53e2010","author":{"name":"Hector Rivas Gandara","email":"7b7e5985d0d5e042df62f31a43aa47b3c2b7c938@gmail.com"},"message":"Fix Close connection for invalid header\n\nRemoteAddr() must close the connection and clear the buffer if we\nreceive a invalid PROXY protocol header.\n\nChange the client test as it can get an EOF or a ECONNRESET.","distinct":true,"url":"https://api.github.com/repos/keymon/go-proxyproto/commits/c264d774d2ac86c2802da7daa57ce015f53e2010"}]}
{"actor":{"display_login":"keymon"}}