Date: Fri, 07 Jan 2022 13:15:56 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 260399] freebsd-update: Downloading patches often fails repeatedly Message-ID: <bug-260399-227-5aw2tgsKZJ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-260399-227@https.bugs.freebsd.org/bugzilla/> References: <bug-260399-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D260399 --- Comment #11 from Some Signup <somesignup@icloud.com> --- My apologies: please note, my last post referred to freebsd-update when on = that occasion I was using portsnap. But I often see the same end result of failed downloads when using freebsd-update - the symptoms are exactly the same.=20 -> 3. The one thing which concerns me here is the HTTP 400 errors; can you reproduce those with HTTP headers I can't reproduce this using curl for an individual file. Looking at my latest attempt at using portsnap I saw this number of errors: 714 400 Error (ignored) 7725 404 Error (ignored) 1 408 Error (ignored) 3 413 Error (ignored) Ignoring the 404 errors thanks to Colin's explanation, the other errors see= m to be important. I thought an http 400 error means a bad request, or a request that the web server cannot handle? I've done a tcpdump while running portsnap --debug auto on a machine. I can attach a part of it. In amongst the 'good' http headers I do see some heade= rs which appear to be 'bad'. A typical 'good' request: GET /bp/22c67764d7b53be769033f98ec4422a47cf71014b47dd893bfd8ba2817a37d38-ce207a= 35bd0fbdb64ac3326e0a2d81e0caf2eb8a9a8c650b11d052a6ea45c2b4 HTTP/1.1 Host: ipv4.aws.portsnap.freebsd.org User-Agent: portsnap (auto, 13.0-RELEASE-p4) Connection: Keep-Alive A bad request: GET /bp/5934ff241e93ae4916c3bd479e032aad2a7bb1e3a3e30c8a0cbe0851d2777ef5-8f7b4d= 39e928d7b3def5c19e2df1bf8986af290a1eac8545b2b134be76258b40 HTTP/1.aws.portsnap.freebsd.org User-Agent: portsnap (auto, 13.0-RELEASE-p4) Connection: Keep-Alive The GET and and Host parts are clobbered together and a spurious '.' is inserted. It looks like the 'HTTP/1.1' is being truncated or overwritten. I= can see this same type of error several times: GET /bp/5e8bc5f6bc657c2e0ca384f617bedd73772f7173a06b64838528832802437619-b24ab5= 58baef9f4a5570bedc48bd720a22e1cd45d1bd38a385730da9d0ddbddb HTTP/1.aws.portsnap.freebsd.org GET /bp/c502e4c30cb2334244f0038351847344ac7452959a913e0972a011dbb8abc0ce-1a4ca6= cb90dab8fae3f2adcec09d82a86d17a20955387dfff3cdf474bbf60c17 HTTP/1.aws.portsnap.freebsd.org GET /bp/955b599e8e767b1a714dabdae3498c0b1e6aaa5f337e058061b8e60fd2a56f5c-4e47c6= 280360287ebc768026f7e60b8b4d97a937d97f7e593c2c689b46c0cb41 HTTP/1.aws.portsnap.freebsd.org GET /bp/298b882b48d8a1d54e99ebfb46d52acb8b757c14d2bcdfcb61e508a015349155-e01fa8= 224d0d5ff8e4b01cc6894dde48f9997229908bd52f4096cb03d58f9f8e HTTP/1.aws.portsnap.freebsd.org ... --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-260399-227-5aw2tgsKZJ>