ΙD: 156419238

Email has been sent to haproxy@formilux.org RBC We reserve all rights.

HAProxy Hostname/Domain used for backend Servers

Hi, I find that HAProxy only resolve DNS of Backend Server that the start up time : * server sv1.mydomain.com *sv1.mydomain.com*:80 check port 80 inter 4000 weight 10 * server sv2.mydomain.com *sv2.mydomain.com*:80 check port 80 inter 4000 weight 10 Even if DNS Server has change the

RE: HAProxy Hostname/Domain used for backend Servers

Hi,  Hi,  I find that HAProxy only resolve DNS of Backend Server that the start  up time :      * server sv1.mydomain.com sv1.mydomain.com:80 check port 80 inter  4000 weight 10  * server sv2.mydomain.com sv2.mydomain.com:80 check port 80 inter  4000 weight 10    Even if DNS Server has

Re: [PATCH] proxy: support use_backend with dynamic names

Great to hear :) I do not work anymore in the same environment, so I can not test the last improvement on this config. it was a generated config file like you with a a few thousand of backend sharing a dozen of frontend. The startup time was about 10 to 15 minutes too. I could rebase my

Re: HAProxy Hostname/Domain used for backend Servers

Hi Lukas, Thank you very much. On 01/04/2014 15:24, Lukas Tribus wrote: Hi, Hi, I find that HAProxy only resolve DNS of Backend Server that the start up time : * server sv1.mydomain.com sv1.mydomain.com:80 check port 80 inter 4000 weight 10 * server sv2.mydomain.com sv2.mydomain.com:80

Re:List - led light

Hi, My friend, Nice day to you! Here is Amy, Sales representative of Lion-leds.com. We are a large manufacturer of LED lighting in China. If you need the price lists, welcome to contact me and offer you more details: sal...@best-led.com . Warm Regards Amy www.lion-leds.com

haproxy ssl questions

Hello, I have couple of haproxy(1.5dev22 snapshot) ssl related questions: Is it possible to use mod_ssl compatible optional_no_ca client cert verify with haproxy: - is it possible to use ca-ignore-err for this. (I think apache 2.2.7(mod_ssl) ignores these errors w/optional_no_ca: #define

Re: haproxy ssl questions

Hi Jarno, some informations available here: http://blog.exceliance.fr/2013/06/13/ssl-client-certificate-information-in-http-headers-and-logs/ and here: http://blog.exceliance.fr/2012/10/03/ssl-client-certificate-management-at-application-level/ concerning nbproc, you should makes all your SSL

Re: haproxy ssl questions

Hi Baptiste, On Tue, Apr 01, Baptiste wrote: Hi Jarno, some informations available here: http://blog.exceliance.fr/2013/06/13/ssl-client-certificate-information-in-http-headers-and-logs/ and here: http://blog.exceliance.fr/2012/10/03/ssl-client-certificate-management-at-application-level/

Haproxy MySQL support

Hi, I am trying to create a panel to create proxies, I was wondering if you will ever add MySQL support for haproxy were you enter something what you want it to configure like then so you can easily create proxies via the database? I am trying to just execute listen Whatever MyServer:3 mode

unsubscribe

haproxy intermittently not connecting to backend

We have an issue with haproxy (1.5-dev22-1a34d57) where it is intermittently not connecting to the backend server. However the behavior it is exhibiting seems strange. The reason I say strange is that in one example, it logged that the client disconnected after ~49 seconds with a connection flags

Re: haproxy intermittently not connecting to backend

Apologies, my mail client went stupid. Here's the log entry unmangled: 198.228.211.13:60848 api~ platform-push/i-84d931a5 49562/0/-1/-1/49563 0/0/0/0/0 0/0 691/212 503 CC-- 4F8E-4624 + GET /1/sync/notifications/subscribe?sync_box_id=12496sender=D7A9F93D-F653-4527-A022-383AD55A1943 HTTP/1.1

BUG/FEATURE? http-request always applied if backend not available

Hi Willy, I'm getting trouble with that sample configuration when backend has no server available : defaults HTTP mode http option httplog log global frontend ft_public bind 0.0.0.0:80 name HTTP bind 0.0.0.0:443 name HTTPS ssl crt foo.pem acl v-local hdr(Host) 203.0.113.42 acl

Re: BUG/FEATURE? http-request always applied if backend not available

Hi Bertrand, Le 01/04/2014 23:10, Bertrand Jacquin a écrit : Hi Willy, I'm getting trouble with that sample configuration when backend has no server available : defaults HTTP mode http option httplog log global frontend ft_public bind 0.0.0.0:80 name HTTP bind 0.0.0.0:443

Re: BUG/FEATURE? http-request always applied if backend not available

Hi Cyril, D'ar meurzh 01 a viz Ebrel 2014 e 23 eur 35, « Cyril Bonté » he deus skrivet : If bk_local has server UP in the farm, and request look like https://203.0.113.42/__bar, then everything is fine, request is nicely handled by bk_local/localhost. http://203.0.113.42/__bar is correctly

Re: BUG/FEATURE? http-request always applied if backend not available

Le 01/04/2014 23:42, Bertrand Jacquin a écrit : Hi Cyril, D'ar meurzh 01 a viz Ebrel 2014 e 23 eur 35, « Cyril Bonté » he deus skrivet : If bk_local has server UP in the farm, and request look like https://203.0.113.42/__bar, then everything is fine, request is nicely handled by

Re: BUG/FEATURE? http-request always applied if backend not available

Le 01/04/2014 23:56, Bertrand Jacquin a écrit : When bk_local/localhost is UP : $ curl -vk -so /dev/null https://203.0.113.42/__bar/ (...) GET /__bar/ HTTP/1.1 User-Agent: curl/7.35.0 Host: 203.0.113.42 Accept: */* HTTP/1.1 200 OK Date: Tue, 01 Apr 2014 21:54:46 GMT * Server Apache is not

Re: BUG/FEATURE? http-request always applied if backend not available

D'ar merc'her 02 a viz Ebrel 2014 e 00 eur 13, « Cyril Bonté » he deus skrivet : Le 01/04/2014 23:56, Bertrand Jacquin a écrit : When bk_local/localhost is UP : $ curl -vk -so /dev/null https://203.0.113.42/__bar/ (...) GET /__bar/ HTTP/1.1 User-Agent: curl/7.35.0 Host: 203.0.113.42

Re: BUG/FEATURE? http-request always applied if backend not available

Le 02/04/2014 00:16, Bertrand Jacquin a écrit : What is adding the Vary and Strict-Transport-Security headers in this second case ? A missing 'http-response set-header' in the previous copy and paste. http-response set-header Vary Accept-Encoding http-response set-header