Hi Willy,
Am 17-01-2019 15:41, schrieb Willy Tarreau:
Hi Aleks,
On Thu, Jan 17, 2019 at 01:02:56PM +0100, Aleksandar Lazic wrote:
> Very likely, yes. If you want to inspect the body you simply have to
> enable "option http-buffer-request" so that haproxy waits for the body
> before executing r
Hi Aleks,
On Thu, Jan 17, 2019 at 01:02:56PM +0100, Aleksandar Lazic wrote:
> > Very likely, yes. If you want to inspect the body you simply have to
> > enable "option http-buffer-request" so that haproxy waits for the body
> > before executing rules. From there, indeed you can pass whatever Lua
>
Hi Willy.
Am 17.01.2019 um 04:25 schrieb Willy Tarreau:
> Hi Aleks,
>
> On Wed, Jan 16, 2019 at 11:52:12PM +0100, Aleksandar Lazic wrote:
>> For service routing are the standard haproxy content routing options possible
>> (path, header, ...) , right?
>
> Yes absolutely.
>
>> If someone want to
Hi Aleks,
On Wed, Jan 16, 2019 at 11:52:12PM +0100, Aleksandar Lazic wrote:
> For service routing are the standard haproxy content routing options possible
> (path, header, ...) , right?
Yes absolutely.
> If someone want to route based on grpc content he can use lua with body
> content
> right?
Hi.
Am 16.01.2019 um 19:02 schrieb Willy Tarreau:
> Hi,
>
> HAProxy 1.9.2 was released on 2019/01/16. It added 58 new commits
> after version 1.9.1.
>
> It addresses a number of lower importance pending issues that were not
> yet merged into 1.9.1, one bug in the cache and fixes some long-standi
Hi,
HAProxy 1.9.2 was released on 2019/01/16. It added 58 new commits
after version 1.9.1.
It addresses a number of lower importance pending issues that were not
yet merged into 1.9.1, one bug in the cache and fixes some long-standing
limitations that were affecting H2.
The highest severity issu
6 matches
Mail list logo