Hi, On Thu, Jul 20, rai...@ultra-secure.de wrote: > I had a very strange situation earlier. > > He have a site behind a haproxy/nginx combination, it has been > working for years. > (It's Windows). > > However, suddenly I get L7 timeouts. > > But curl to the healthcheck URL works perfectly. > > The output I get looks like this: > > ��server_up > > Piping curl through cat -v looks like this: > > M-^?M-~s^@e^@r^@v^@e^@r^@_^@u^@p^@^M^@ > ^@ > > They have started to generate this file via a powershell script and > it has inserted a byte-order-mark into the file (BOM). > Took a while to figure this out ;-) > > haproxy 1.6.9 (FreeBSD 10-amd64) seems to actually choke on these > files and hang - I had to kill -9 it. > > After replacing the file with its previous, ASCII-only copy, > everything started to work again. > > Can anyone reproduce this?
Can you share how you've configured health checks in haproxy.cfg ? And can you show curl -v output of the BOM response and od -c bomfile. > Maybe it's fixed in later versions? (AFAIK 1.6.13 has some freebsd related fixes (http://www.haproxy.org/download/1.6/src/CHANGELOG)). (https://www.mail-archive.com/haproxy@formilux.org/msg25807.html) -- Jarno Huuskonen
