On 4/15/22 06:40, Shawn Heisey wrote:
The 403 is random. While clicking around in my webmail, going to
different folders, I occasionally see a red box that has an error
message pop up, an error message I can't recall at the moment. That's
when the 403 is logged.
I noticed there was another
Hi David,
Done reviewing/editing/testing/merging both patches now.
Thanks!
Willy
On 4/15/2022 1:20 AM, Amaury Denoyelle wrote:
Hum this is strange. Do you have a way to reproduce it easily ?
The 403 is random. While clicking around in my webmail, going to
different folders, I occasionally see a red box that has an error
message pop up, an error message I can't recall at
Hi Marno & Roberto,
You can simply redirect to the matching frontend port by not specifying
a port in the backend, it will automatically hit the same port that was
used in the front-end connection. That should make for a much cleaner
configuration
It's documented in section 2.5
On Thu, Apr 14, 2022 at 07:29:20AM -0600, Shawn Heisey wrote:
> On 4/14/22 03:27, Amaury Denoyelle wrote:
> > So to summary, this option should be activated if you only have browsers
> > as client and the traffic is big enough to saturate haproxy queues.
> > I hope this will clarify your thoughts,
Hey Roberto,
Yes, there is a misconfiguration in both config snippets that you sent:
frontend Frontend_FTP
bind *:21
bind *:2-20010
mode tcp
option tcplog
timeout client 1h
default_backend HAProxy_BE
backend HAProxy_BE
mode tcp
server HAProxy-Node-2
6 matches
Mail list logo