Re:Corn bulb/250W

Hi Manager, Good day! We export led lights with reasonable price and top quality from 2008 in China.  Hope can be a partner of your company in the near future! If you are interested, I'll send you our catalogue! thanks in advance!

Re: Looking for help about "req.body" logging

Did anyone succeeded in logging req.body? If so I would likely appreciate an example / some hints / a pointer into the docs, even though I've looked into this last one and could not find how to do it. Thank you Alberto On Fri, 16 Oct 2015 at 10:40 Alberto Zaccagni <

Jacquline Resume_id:4580

Hello!!! my name is Jacquline Radcliffe my resume is doc file I would appreciate your immediate attention to this matter Yours faithfully Jacquline Radcliffe my_resume_0474.doc Description: MS-Word document

Upgrade from 1.4 -> 1.6, any gotchas?

I'll be doing an upgrade from 1.4 to 1.6 tomorrow. Just wondering if there are any changed defaults, breaking changes, anything like that? Or should my config work as before? Thank you!

Re: Upgrade from 1.4 -> 1.6, any gotchas?

On Wed, Oct 21, 2015 at 7:14 PM, SL wrote: > I'll be doing an upgrade from 1.4 to 1.6 tomorrow. Just wondering if there > are any changed defaults, breaking changes, anything like that? Or should > my config work as before? Haproxy 1.5 changed the default connection mode if

RE: Upgrade from 1.4 -> 1.6, any gotchas?

> On Wed, Oct 21, 2015 at 7:14 PM, SL wrote: >> I'll be doing an upgrade from 1.4 to 1.6 tomorrow. Just wondering if there >> are any changed defaults, breaking changes, anything like that? Or should >> my config work as before? > > Haproxy 1.5 changed the default connection

Re: [PATCH] MEDIUM: dns: Don't use the ANY query type

On Wed, Oct 21, 2015 at 1:24 PM, Lukas Tribus wrote: > Hi Robin, > > >> Hey guys, >> >> Actually when you get an NXDOMAIN reply you can just stop resolving that >> domain. Basically there are 2 types of "negative" replies in DNS: >> >> NODATA: basically this is when you don't

Re: Upgrade from 1.4 -> 1.6, any gotchas?

Hi all, Le 21/10/2015 22:16, Lukas Tribus a écrit : On Wed, Oct 21, 2015 at 7:14 PM, SL wrote: I'll be doing an upgrade from 1.4 to 1.6 tomorrow. Just wondering if there are any changed defaults, breaking changes, anything like that? Or should my config work as before?

Re: Looking for help about "req.body" logging

Hi, I guess this is because the sample applies to a request element while logging happens after the response has been sent, so data is not available anymore. Look for capture in this page http://blog.haproxy.com/2015/10/14/whats-new-in-haproxy-1-6/ and use it to capture the body at the request

Multiplexing multiple services behind one agent (feature suggestion; patch attached)

Hello haproxy@: My name is James Brown; I wrote a small piece of software called hacheck (https://github.com/Roguelazer/hacheck) which is designed to be a healthcheck proxy for decentralized load balancer control (remove a node from a load balancer without knowing where the load balancers are;

Re: [PATCH] MEDIUM: dns: Don't use the ANY query type

Hey guys, Actually when you get an NXDOMAIN reply you can just stop resolving that domain. Basically there are 2 types of "negative" replies in DNS: NODATA: basically this is when you don't get an error (NOERROR in dig), but not the actual data you are looking for. You might have gotten some

10.1" Panel PC Android 4.2.2

This is a multi-part message in MIME format. Thismessagecontainsgraphics.Ifyoudonotseethe=graphics,c=lickheretoview.Formoredetailsinformationabout10.1=HMI,Pleasevisitourwebsite:www.ewinsonic.com88633704789=88633704722sa...@ewinsonic.com

RE: [PATCH] MEDIUM: dns: Don't use the ANY query type

Hi Robin, > Hey guys, > > Actually when you get an NXDOMAIN reply you can just stop resolving that > domain. Basically there are 2 types of "negative" replies in DNS: > > NODATA: basically this is when you don't get an error (NOERROR in dig), > but not the actual data you are looking for. You

1.6.1: No Error regarding: 'Cannot Create Listening Socket'

Dear Willy, Thank you for your additional guidance. Here is the information you requested: 1) 1.6.1 starts up smoothly and remains stable. 2) To be responsive to your previous query about 1.6.0 with your fixns.diff patch, it still gives listening socket for ‘listen haproxystats’ block