Re: RFC: HAProxy shared health-check for nbproc > 1

On Wed, Feb 15, 2017 at 10:58:02AM +0530, Krishna Kumar (Engineering) wrote: > Hi Willy, > > Thanks for your comments, I did not realize that this was discussed earlier. > > Let me go through your feedback and get back. Sorry that I am taking time > for this, but this is due to work related

Re: Return codes from proxy

Le 15/02/2017 à 00:10, Birdwell, Rob a écrit : Hi Cyril! Responses below: Are you really sure you're making the same request on the application side (access logs should give you a hint) ? Positive. I’m making the curl request directly from the Apache HTTP server & HAProxy server. The

Re: RFC: HAProxy shared health-check for nbproc > 1

Hi Willy, Thanks for your comments, I did not realize that this was discussed earlier. Let me go through your feedback and get back. Sorry that I am taking time for this, but this is due to work related reasons. Regards - Krishna On Tue, Feb 14, 2017 at 2:44 PM, Willy Tarreau

Opinion about blog post of SPOE

Hi. Due to the fact that I like this SPOE I have started to write about it ;-) https://me2digital.online/2017/02/15/haproxy-1-7-feature-spoe/ Is the concept displayed correct in the picture? Are the data (tcp, http-header, http-body) quoted when HAProxy send it to the SPOEA? I'm

Re: Introduction and small changes to HAProxy for adding custom errorfiles for 401 and 407 http status page

Am 13-02-2017 23:10, schrieb Willy Tarreau: On Mon, Feb 13, 2017 at 10:50:36PM +0100, Aleksandar Lazic wrote: What I mean is that. haproxy have already a config parser. Why not use this config parser and add new keyword for error files. With this approach the customers can reuse there

Re: Return codes from proxy

This information may also help: haproxy -vv HA-Proxy version 1.6.11 2016/12/25 Copyright 2000-2016 Willy Tarreau Build options : TARGET = linux2628 CPU = native CC = gcc CFLAGS = -O2 -march=native -g -fno-strict-aliasing -Wdeclaration-after-statement

Re: Return codes from proxy

Hi Cyril! Responses below: Are you really sure you're making the same request on the application side (access logs should give you a hint) ? Positive. I’m making the curl request directly from the Apache HTTP server & HAProxy server. The details for the HAProxy curl are in the thread way

Re: Return codes from proxy

Le 14/02/2017 à 22:20, Birdwell, Rob a écrit : Thanks for the quick reply Cyril! You’re correct on both counts; this is a test config & the large timeout will definitely not be kept. For the http-server-close, that was a mistake on my part; thank you for noticing that. I’ve tried the

RE: Issue with windows IE 11 and Edge

Understood - thanks for the reply. I will set a reminder for myself to send something next week. -Original Message- From: Willy Tarreau [mailto:w...@1wt.eu] Sent: Tuesday, February 14, 2017 4:54 PM To: Stroehmann, James Cc: 'haproxy@formilux.org'

Re: Issue with windows IE 11 and Edge

Hi James, On Tue, Feb 14, 2017 at 09:10:00PM +, James Stroehmann wrote: > Is there other information I can provide to help troubleshoot this? The only thing which will work will be a network capture to understand what the requests *really* look like. You don't need to send it to the list, a

Re: Return codes from proxy

Thanks for the quick reply Cyril! You’re correct on both counts; this is a test config & the large timeout will definitely not be kept. For the http-server-close, that was a mistake on my part; thank you for noticing that. I’ve tried the configuration both ways (as far as

RE: Issue with windows IE 11 and Edge

Is there other information I can provide to help troubleshoot this? -Original Message- From: Stroehmann, James Sent: Monday, January 16, 2017 5:26 PM To: Willy Tarreau Cc: 'haproxy@formilux.org' Subject: RE: Issue with windows IE 11 and Edge Just

Re: Last character in log lines is space

Hi John, Le 14/02/2017 à 19:57, John Dison a écrit : Hello, I am writing haproxy (1.6.9) logs via syslog: global log /dev/loglocal0 debug alert local0.*/var/log/haproxy.log I just noticed that last character of each line is space: 46

Re: Return codes from proxy

Hi Rob, Le 14/02/2017 à 20:23, Birdwell, Rob a écrit : Hello, I was curious if someone would be able to assist with return codes from HAProxy. Currently, we are able to receive a 201 for a reverse proxy solution from Apache HTTP, but when utilzing HAProxy, only a 200 is received utilizing

Return codes from proxy

Hello, I was curious if someone would be able to assist with return codes from HAProxy. Currently, we are able to receive a 201 for a reverse proxy solution from Apache HTTP, but when utilzing HAProxy, only a 200 is received utilizing an identical cURL command. The current HAProxy/Apache

Re: Haproxy issue

Just adding this back to the list. > On 14. Feb. 2017, at 18:12, > wrote: > > Ok thank you for your reply ! > I found my error > Haproxy was not happy with http request > > I was doing https://test-rest.net:8089

Re: Haproxy issue

Hi! >> frontend rest-in >> >> bind *:8089 ssl crt /etc/ssl/* >> >> acl host_rest_services hdr(Host) -i test-rest.net >>

Re: Haproxy issue

On February 14, 2017 at 10:46:05, thibault.dai...@orange.com (thibault.dai...@orange.com) wrote: Hi, I’ve got an issue with Haproxy conf need help please !! See my haproxy.cfg frontend rest-in bind *:8089 ssl crt /etc/ssl/* reqadd

Haproxy issue

Hi, I've got an issue with Haproxy conf need help please !! See my haproxy.cfg frontend rest-in bind *:8089 ssl crt /etc/ssl/* reqadd X-Forwarded-Proto:\ https acl host_rest_services hdr(Host) -i test-rest.net use_backend rest_services if host_rest_services

Removing the cpu-map cpu/-set limit?

Hi, there is currently a limit for both, the process number itself as well as the cpu/-set. Wouldn't it make sense to lift the cpu/-set limit? Example: I've got a 18 Core / 36 Thread (72 with HT) CPU Now I want to use non-HT threads (e.g. all even threads) for which I may have to go beyond

Re: ACL randomly failing

On Tue, Feb 14, 2017 at 11:36:14AM +0100, Cyril Bonté wrote: > > De: "Willy Tarreau" > > À: "Mathieu Poussin" > > Cc: "Daniel Schneller" , > > "haproxy+h...@formilux.org" > > Envoyé: Mardi 14 Février

Re: ACL randomly failing

> De: "Willy Tarreau" > À: "Mathieu Poussin" > Cc: "Daniel Schneller" , > "haproxy+h...@formilux.org" > Envoyé: Mardi 14 Février 2017 10:18:30 > Objet: Re: ACL randomly failing > > On Tue, Feb 14, 2017

Re: ACL randomly failing

On Tue, Feb 14, 2017 at 10:04:30AM +0100, Mathieu Poussin wrote: > Ok I just found why, ports can be shared because of SO_REUSEADDR... What's a > surprise :) SO_REUSEPORT to be precise :-) > Is there a way to force disable the use of this flag by HAProxy ? We merged a patch for this recently,

Re: RFC: HAProxy shared health-check for nbproc > 1

Hi Krishna, On Tue, Feb 14, 2017 at 12:45:31PM +0530, Krishna Kumar (Engineering) wrote: > Hi Willy, > > Some time back, I had worked on making health checks being done by only > one HAProxy process, and to share this information on a UP/DOWN event to > other processes (tested for 64 processes).

Re: ACL randomly failing

Ok I just found why, ports can be shared because of SO_REUSEADDR… What’s a surprise :) Is there a way to force disable the use of this flag by HAProxy ? > On 14 Feb 2017, at 09:58, Mathieu Poussin wrote: > > Hello Daniel. > > I just checked that and you are right. > I

Re: ACL randomly failing

Hello Daniel. I just checked that and you are right. I had both the legacy haproxy 1.4 (/usr/sbin/haproxy) and the compiled 1.7 (/usr/local/sbin/haproxy) running for an unknown reason… The most surprising thing is that they were both listening to the same ports… Aren’t socket binding supposed