[no subject]

2016-02-29 Thread promotion
Title: Tai wah Hi Customer,If you can not see the description below, please click here. 如無法閱讀以下的內容,請按此.To learn more, please visit www.hk-printing.com.hk. 想了解多D請到www.hk-printing.com.hkProfessional one stop service printing company & More than 16 year experience

Re: Haproxy, Internet Explorer and sporadic 408 response

2016-02-29 Thread Aleksandar Lazic
Hi. Am 29-02-2016 12:35, schrieb Dennis Jacobfeuerborn: Hi, I'm getting reports that occasionally IE users see 408 error when calling out Site but the behavior is not easily reproducible. I found something about this Problem in the archives:

Re: [PATCH] CLEANUP: log

2016-02-29 Thread Willy Tarreau
Hi David, On Mon, Feb 29, 2016 at 07:55:45PM +, David CARLIER wrote: > Hi I hope this looks better this time. Yes, thanks. I'll split it in two, one for the API update and the other one for the logs. That way it's easier to know what to backport when we later clean up all other call places.

Re: [PATCH] CLEANUP: log

2016-02-29 Thread David CARLIER
Hi I hope this looks better this time. Kindest regards. On 29 February 2016 at 11:49, David CARLIER wrote: > Sorry I did not see the whole email, just realized ok why not :-) > > On 29 February 2016 at 11:18, Willy Tarreau wrote: > >> On Mon, Feb 29, 2016 at

Logging SSL request information in TCP mode

2016-02-29 Thread Peter Pramberger
Hi, I recently tried to enhance the logs with SSL information for HAProxy 1.6.3 running in TCP mode for SSL forwarding. While using the SSL session ID for session persistence across the backend servers works great, I was not able to make HAProxy log the SSL version and SNI hostname from the

Logging binary data in log-format and X flag

2016-02-29 Thread Peter Pramberger
Hi, I'm currently using HAProxy 1.6.3 in a SSL termination setup and recently tried to add the SSL session ID to the log output. According to the documentation I understood that using the X flag would convert the content to readable hex format, but using this logs only garbage: log-format

Re: SNI configuration

2016-02-29 Thread Alexey Vlasov
This is my mistake. The option "strict-sni" works right. On Fri, Feb 26, 2016 at 03:39:24PM +0300, Alexey Vlasov wrote: > Hi, > > Thank you for your answer! > > Yes, it seems that this option is what I actually need. But > unfortunatelly it doesn't work every time. > > The following is right

Re: [PATCH] CLEANUP: log

2016-02-29 Thread David CARLIER
Sorry I did not see the whole email, just realized ok why not :-) On 29 February 2016 at 11:18, Willy Tarreau wrote: > On Mon, Feb 29, 2016 at 10:37:33AM +, David CARLIER wrote: > > Hi no problems it is not a bugfix at all, usually just better to copy a > > const char instead

Re: Proliferation of processes under systemd wrapper

2016-02-29 Thread Conrad Hoffmann
Hi, On 02/27/2016 02:23 AM, BR Kumar wrote: > Hi Conrad, > > Thanks for responding. Regarding point (2), I'm not sure the last level of > child processes are awaiting connection closure and would exit afterwards. > In my test, netstat showed no connection against the haproxy port. Yet, the >

Haproxy, Internet Explorer and sporadic 408 response

2016-02-29 Thread Dennis Jacobfeuerborn
Hi, I'm getting reports that occasionally IE users see 408 error when calling out Site but the behavior is not easily reproducible. I found something about this Problem in the archives: http://comments.gmane.org/gmane.comp.web.haproxy/15263 The proposed workaround mentioned there is to add the

Re: [PATCH] CLEANUP: log

2016-02-29 Thread Willy Tarreau
On Mon, Feb 29, 2016 at 10:37:33AM +, David CARLIER wrote: > Hi no problems it is not a bugfix at all, usually just better to copy a > const char instead of casting it in this sort of situation. Nothing else. Yes clearly, but as I said it's better to fix it anyway. Are you interested in

Re: [PATCH] CLEANUP: log

2016-02-29 Thread David CARLIER
Hi no problems it is not a bugfix at all, usually just better to copy a const char instead of casting it in this sort of situation. Nothing else. Best regards. On 28 February 2016 at 22:58, Willy Tarreau wrote: > Hi David, > > Sorry for the delay, but each time I looked at it I