On 10/25/22 20:55, Matthew H wrote:
I have included the requested output from tcpdump below:
Thank you! This raw output is sufficient to determine that no transfer
encoding was used by this buggy origin server. I have updated the GitHub
comment/summary accordingly.
N.B. In the future, plea
Hi all,
Thanks for the replies.
I have included the requested output from tcpdump below:
tcpdump -A -s 0 -ni enp4s0 "host 159.203.14.9 and (((ip[2:2] -
((ip[0]&0xf)<<2)) - ((tcp[12]&
0xf0)>>2)) != 0)"
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on enp4s0,
On 10/23/22 20:36, Matthew H wrote:
Hi,
I'm using Squid to proxy HTTP requests to another proxy. I can see squid
sending the request to the parent and getting a response, but it sends
the client that initiated the request a 502 Bad Gateway response.
On closer inspection it appears the parent
On 2022-10-24 13:36, Matthew H wrote:
Hi,
I'm using Squid to proxy HTTP requests to another proxy. I can see
squid
sending the request to the parent and getting a response, but it sends
the
client that initiated the request a 502 Bad Gateway response.
That is correct behaviour. Squid does n
Hi,
I'm using Squid to proxy HTTP requests to another proxy. I can see squid
sending the request to the parent and getting a response, but it sends the
client that initiated the request a 502 Bad Gateway response.
On closer inspection it appears the parent proxy is sending an
empty transfer-encod
