Le 10/19/21 à 16:49, Jim Freeman a écrit :
OK - this is weird (so don't shoot the messenger?).
With more tcpdump-ing and examination, the back-end service logs that it sent a
response, but
1) tcpdump running on the haproxy instance never sees the response !
a) 2 proxies - an AWS ELB
OK - this is weird (so don't shoot the messenger?).
With more tcpdump-ing and examination, the back-end service logs that it
sent a response, but
1) tcpdump running on the haproxy instance never sees the response !
a) 2 proxies - an AWS ELB and on-instance nginx - lie between HAProxy
Many thanks for your insight and response - I'll check that out.
On Tue, Oct 19, 2021 at 3:24 AM Christopher Faulet
wrote:
> Le 10/13/21 à 8:30 PM, Jim Freeman a écrit :
> > In adding a couple of new security response headers via haproxy.cfg (one
> is 112
> > bytes, the other 32), a few
Le 10/13/21 à 8:30 PM, Jim Freeman a écrit :
In adding a couple of new security response headers via haproxy.cfg (one is 112
bytes, the other 32), a few requests are now getting 500 status (PH session
state) responses, but "show errors" has 0 entries? Most responses succeed (all
have the
Nope - never mind. Plenty of successful traffic with the sec-ch-ua*
headers.
I'll keep poking re: PH/500 w/o "show errors", and confess here when/how I
find it is the result of being ignernt.
On Mon, Oct 18, 2021 at 11:41 AM Jim Freeman wrote:
> Ran tcpdump on the proxy in search of useful
Ran tcpdump on the proxy in search of useful detail.
Saw these unfamiliar (to me) headers on the PH/500 'd request :
sec-ch-ua: " Not A;Brand";v="99", "Chromium";v="90"
sec-ch-ua-mobile: ?0
Googled, found : https://www.chromium.org/updates/ua-ch, was a tad FUD'd by
===
Possible Site
In adding a couple of new security response headers via haproxy.cfg (one is
112 bytes, the other 32), a few requests are now getting 500 status (PH
session state) responses, but "show errors" has 0 entries? Most responses
succeed (all have the additional headers), so it's not a problem with the
7 matches
Mail list logo
