Lukas, The folks that access our service via the ColdFusion CFHTTP method report errors, because those calls fail, and thus they are not getting the requested data.
-- Thomas Best, Thomas Amsler http://gplus.to/tamsler On Thu, Oct 17, 2013 at 10:41 AM, Lukas Tribus <[email protected]> wrote: > Hi Thomas! > > > We are using HAProxy v1.5-dev19, and are seeing a lot of the following > > errors in our haproxy logs: > > > > <-- snip --> > > Oct 16 02:24:22 localhost haproxy[2473]: <some ip>:44950 > > [16/Oct/2013:02:24:22.643] https-in/1: SSL handshake failure > > Oct 16 02:30:47 localhost haproxy[2473]: <some ip>:37530 > > [16/Oct/2013:02:30:47.436] https-in/1: SSL handshake failure > > Oct 16 02:32:09 localhost haproxy[2473]: <some ip>:32930 > > [16/Oct/2013:02:32:08.709] https-in/1: SSL handshake failure > > Oct 16 02:32:28 localhost haproxy[2473]: <some ip>:38069 > > [16/Oct/2013:02:32:27.731] https-in/1: SSL handshake failure > > <-- snip --> > > > > This error occurs at a rate of 0.7%. It most often happens via > > ColdFusion CFHTTP connections. Could there be any issues with HAProxy > > or is this a client connection issue? > > Did you have an actual customer reporting issues or are you just seeing > this errors in the log? > > Until you have a reported and confirmed issue, I wouldn't worry too much. > Clients may do bogus things, have transient network issues or simply die. > All those things may generate the error above. > > Other software simply doesn't show you those errors. > > > > Lukas
