Hey there,
i am having a problem, with a request, that goes to caddy, which then does reverse_proxy to an application.
the request has super large headers (not good but, cannot change ).
when sending the request to my app, without using caddy, the application receives - handles and responses the request.
same request via caddy, i get 502 from caddy
{"level":"error","ts":1714418727.1089869,"logger":"http.log.error","msg":"EOF","request":{"remote_ip":"10.1.75.1","remote_port":"5093","client_ip":"10.1.75.1","proto":"HTTP/1.1","method":"GET","host":"talk.krone.at","uri":"/api/v1/auth","headers":{"Sec-Ch-Ua":["\"Google Chrome\";v=\"123\", \"Not:A-Brand\";v=\"8\", \"Chromium\";v=\"123\""],"Sec-Ch-Ua-Platform":["\"Android\""],"Sec-Fetch-Site":["same-origin"],"Authorization":[],"Content-Type":["application/json"],"Pragma":["no-cache"],"Accept":["application/json"],"Accept-Language":["de-AT,de-DE;q=0.9,de;q=0.8,en-US;q=0.7,en;q=0.6"],"Cookie":[],"Referer":["https://talk.krone.at/embed/stream?asset_url=https%3A%2F%2Fwww.krone.at%2F3350461&initialWidth=382&childId=coral-container&parentTitle=Auf%20Firmenareal%20-%20Zw%C3%B6lf%20E-Autos%20in%20Flammen%3A%20Brandstiftung%20vermutet%20%7C%20krone.at&parentUrl=https%3A%2F%2Fwww.krone.at%2F3350461%23comment-list"],"Sec-Fetch-Dest":["empty"],"Sec-Fetch-Mode":["cors"],"User-Agent":["Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/123.0.0.0 Mobile Safari/537.36"],"Cache-Control":["no-cache"],"Sec-Ch-Ua-Mobile":["?1"]},"tls":{"resumed":false,"version":771,"cipher_suite":49199,"proto":"http/1.1","server_name":"hja-api.krone.at"}},"duration":0.001549574,"status":502,"err_id":"xci5dapqj","err_trace":"reverseproxy.statusError (reverseproxy.go:1267)"}
when i tcpdump
on my application, i see the request arriving, but the headers are truncated.
current state of documentation is wild, we are using latest caddy2 with caddyfile.
not sure which limit it reaches - and what of the many config options might do the trick.
regards
helmut