[squid-users] Empty transfer-encoding header causes 502 response

[Matthew H]

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-encoding header, and this is causing Squid to send a 502. Is
there any way to ignore this? It looks like its enforced in
HttpHeader.cc#L510
<https://github.com/squid-cache/squid/blob/5139f0f64a4d7bba0d91d631b031c4700e7576b4/src/HttpHeader.cc#L510>

I'm using Squid 5.6, or more specifically the ubuntu/squid:5.6-22.10_edge
docker image.

I've included the logs below.

Thanks
Matthew

2022/10/24 00:23:59.106| ctx: enter level  0: 'http://nintendo.com/'
2022/10/24 00:23:59.106| 11,3| http.cc(666) processReplyHeader:
processReplyHeader: key '19010000000000000C00000000000000'
2022/10/24 00:23:59.106| 11,2| http.cc(720) processReplyHeader: HTTP Server
conn294 local=172.25.0.3:57802 remote=159.203.14.9:1996 FIRSTUP_PARENT FD
26 flags=1
2022/10/24 00:23:59.106| 11,2| http.cc(721) processReplyHeader: HTTP Server
RESPONSE:
---------
HTTP/1.1 200 OK
x-powered-by: Express
content-type: text/html; charset=iso-8859-1
transfer-encoding:
date: Mon, 24 Oct 2022 00:23:57 GMT
connection: close

----------
2022/10/24 00:23:59.106| 55,3| HttpHeader.cc(882) getList: empty list
header: Transfer-Encoding(Transfer-Encoding[63])
2022/10/24 00:23:59.106| 55,2| HttpHeader.cc(559) parse: WARNING:
unsupported Transfer-Encoding used by client:
2022/10/24 00:23:59.106| ctx: exit level  0
2022/10/24 00:23:59.106| 20,3| store.cc(1673) reset: http://nintendo.com/
2022/10/24 00:23:59.107| 17,3| FwdState.cc(492) fail: ERR_INVALID_RESP "Bad
Gateway"
        http://nintendo.com/
2022/10/24 00:23:59.107| 17,3| FwdState.cc(533) unregister:
http://nintendo.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20221024/4a082b13/attachment.htm>