From bfa88e9b1c0ecf010aab8f28c4032203245b519e Mon Sep 17 00:00:00 2001 From: James Shubin Date: Fri, 30 Aug 2024 20:33:41 -0400 Subject: [PATCH] engine: resources: Workaround regression in wget2 Apparently wget2 has a serious regression that the HTTP 102 header throws it off... So let's not send this for now... I'm pretty unhappy about this, wget used to always be rock solid. Maybe curl deserves a chance? (This works fine with curl btw.) --- engine/resources/http_proxy.go | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/engine/resources/http_proxy.go b/engine/resources/http_proxy.go index 4ad090b9..48137440 100644 --- a/engine/resources/http_proxy.go +++ b/engine/resources/http_proxy.go @@ -196,7 +196,8 @@ func (obj *HTTPProxyRes) serveHTTP(ctx context.Context, requestPath string) (han // Tell the client right away, that we're working on things... // TODO: Is this valuable to give us more time to block? - w.WriteHeader(http.StatusProcessing) // http 102, RFC 2518, 10.1 + // NOTE: Using this header breaks wget2! + //w.WriteHeader(http.StatusProcessing) // http 102, RFC 2518, 10.1 response, err := client.Do(request) // (*Response, error) if err != nil {