Did you miss the two mails from Igor containing suggestions?
Like this email, they went both to the list and directly to yourself. Maybe
check your spam folder.
On Sat, 11 Aug 2018 at 02:28, Jonathan Opperman wrote:
> On Tue, 7 Aug 2018, 11:43 Jonathan Opperman,
On Tue, 7 Aug 2018, 11:43 Jonathan Opperman, wrote:
> Hi All,
> I am hoping someone can give me some tips and pointers on getting
> something working
> in haproxy that could do the following:
> I have installed haproxy and put a web server behind it, the proxy has 2
On Fri, Aug 10, 2018 at 09:54:38AM -0400, Patrick Hemmer wrote:
> Merge it!
> Quite happy to see this done with. Any issues can be addressed as bug fixes.
Yes, same here. I've updated the ROADMAP file to remove this 8-years
old entry :-)
On 2018/8/10 09:19, Willy Tarreau wrote:
> Hi Patrick,
> On Thu, Aug 09, 2018 at 06:29:33PM -0400, Patrick Hemmer wrote:
>> I also went and removed the queue position counter code from
>> stream_process_counters(), and the logging still appears to work fine
>> (but I could have easily missed
On Thu, Aug 09, 2018 at 06:29:33PM -0400, Patrick Hemmer wrote:
> I also went and removed the queue position counter code from
> stream_process_counters(), and the logging still appears to work fine
> (but I could have easily missed some potential scenarios).
> In regards
Thankyou Thierry for your reply. I will change to txn.f[‘req.fhdr’].
On Wed, Aug 1, 2018 at 2:31 PM, Thierry Fournier <
> The Lua overhead is very low. On my laptop I reach easyly 18 000 HTTP
> requests by seconds with basic Lua processing. I guess
Marcos Moreno reported recently that an "haproxy -c -f " would
succeed even if some servers points to a "resolvers" section which does not
Then, starting up haproxy would fail, with the expected message "resolvers
section not found".
The patch in attachment fixes this behavior.
On Fri, Aug 10, 2018 at 12:57 AM, Anthony Vuong
> I seem to possibly be missing the obvious here. But wondering if anyone
> can shed some light.
> I'm trying to have different url paths be routed to different backends.
> frontend testdomain
> bind 172.16.0.17:80
Mail list logo