2024 à 08:18, Marcello Lorenzi a écrit :
> > Hi Christopher,
> > thanks for the response. The first issue is related to the zero-copy
> forwarding
> > configuration and we noticed the issue
> > https://github.com/haproxy/haproxy/issues/2387
> > <https://github.co
critto:
> Le 04/01/2024 à 14:55, Marcello Lorenzi a écrit :
> > Hi all,
> > we installed haproxy 2.9 on our development environment and we noticed
> an issue
> > on a zip download request. If we tried to download a 27 MB file passing
> through
> > haproxy the request h
Hi all,
we installed haproxy 2.9 on our development environment and we noticed an
issue on a zip download request. If we tried to download a 27 MB file
passing through haproxy the request has been served to the client with a
200 response but the file size was truncated (3-5mb). We installed
Hi All,
we use haproxy 2.2.17-dd94a25 in our development environment and we
configure a backend with proxy protocol v2 to permit the source IP
forwarding to a TLS backend server. All the configuration works fine but we
notice this error reported on backend Apache error logs:
AH03507:
Hi All,
We're experiencing an issue on our haproxy 2.2 instance. We configured some
backends and all worked fine but if we tried to forward some requests with
the header Origin we received a 403 error, but we didn't have any extra
config.
Could you help us to identify the issue?
Thanks,
Marcello
is not present.
tcp0 0 0.0.0.0:112110.0.0.0:*
LISTEN -off (0.00/0/0)
Marcello
On Fri, May 11, 2018 at 12:20 PM, Jarno Huuskonen <jarno.huusko...@uef.fi>
wrote:
> Hi,
>
> On Fri, May 11, Marcello Lorenzi wrote:
> > we are checking the p
Hi All,
we are checking the possibility to balance some memcached instances with an
HAProxy 1.8 instance but we need to implement the keepalive on TCP Listen
port. If we use the command "netstat -ano" we noticed that memcached
configure the keepalive on the connection but not HAProxy. Could you
Hi All,
i'm testing a TPROXY implementaion on RHEL 7 KVM servers but i noticed some
issue. All the connections are collected by the VLAN 192.168.10.0/24 and
the backend communication between HAPROXY and APACHE are perfomed on VLAN
192.168.20.0/24. The IP addresses are
192.168.10.20 fe01-dmz
Hi All,
i'm trying to configure a test Haproxy TPROXY instance on centos 6.5
boxes. The HAproxy has a card connected to 192.168.10.0/24 VLAN and on
connected to 192.168.20.0/24. The webserver is only connected to
192.168.20.0/24 VLAN.
When I tried to active Tproxy configuration on the
9 matches
Mail list logo