Linux APT repository serving bad header data

RogueScholar commented 2 years ago

So this is what I've been seeing for the last week or so with the beta APT repository enabled in my sources.list.d directory:

$ sudo apt update
  …
  Ign:237 https://download.wavebox.app/beta/linux/deb amd64/ InRelease
  …
  Err:237 https://download.wavebox.app/beta/linux/deb amd64/ InRelease
  The HTTP server sent an invalid Content-Range header Bad header data [IP: 2606:4700:3030::6815:2816 443]
  …
  W: Failed to fetch https://download.wavebox.app/beta/linux/deb/amd64/InRelease  The HTTP server sent an invalid
  Content-Range header Bad header data [IP: 2606:4700:3030::6815:2816 443]

I'm rather curious to learn exactly what the nature of the invalid Content-Range value is, but if you'd rather just fix it on your end and never speak of it for as long as we both shall live, I'm totally cool with that. too. Here's what I'm able to offer towards ameliorating the situation...

The relevant IETF document is RFC 7233, specifically Section 4 which treats on instances of responding to range requests.
Since 2017, APT only parses the Content Range header field within code 206 and 416 HTTP responses.

The output of curl -6LD - "https://download.wavebox.app/beta/linux/deb/amd64/InRelease" is as follows:

HTTP/2 200 
date: Thu, 03 Feb 2022 07:56:25 GMT
content-type: application/octet-stream
content-length: 1775
cf-ray: 6d7a1a41bf252509-SJC
accept-ranges: bytes
cache-control: max-age=0, no-cache, no-store
cf-cache-status: DYNAMIC
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
x-bz-content-sha1: 37579c3f018cd555952baa3b38f26d3b8f8d822b
x-bz-file-id: 4_z9bdd280965563be36ade0317_f1171971722d0e8ac_d20220202_m145150_c000_v0001082_t0032
x-bz-file-name: beta/linux/deb/amd64/InRelease
x-bz-info-src_last_modified_millis: 1643813260383
x-bz-upload-timestamp: 1643813510000
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3? s=T8PIHxjDs0zR2%2FRKcRBFJxve%2FH6Z9QelBV8sBs%2FaQWqlRxV4d2Id1XqZbyzIBbSUKo0zJce5sO3tE5tP9BU6L3jYotqHr59mkB2YAlDRvlaO3Ie77bOX%2FOKe0yVg8fmN5zf4wSilVgJ0U%2BqQrVkhoDqTZA%3D%3D"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
server: cloudflare
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Architectures: amd64
Date: Wed, 02 Feb 2022 14:47:40 +0000
Suite: amd64
MD5Sum:
9cc956c981b5ba2911436c1c9082e4cd            13378 Packages
9e5c1aec47f6804fc640b7a64fc372e4             2517 Packages.gz
d41d8cd98f00b204e9800998ecf8427e                0 Release
SHA1:
bbb90db156a3c8829df887f94bfbaa15368a1c6f            13378 Packages
9e5d43c57a27283f14ae03acf3aab5e9b41a3450             2517 Packages.gz
da39a3ee5e6b4b0d3255bfef95601890afd80709                0 Release
SHA256:
4d745e3428d08963b393d1cf5ac5d40ef41f1e09b71ed7679a7173f28143f1f7            13378 Packages
0012efa6974fab8b76eaaeaaf68598b997d323e1cce852827044ca7e57aacaaa             2517 Packages.gz
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855                0 Release
SHA512:
44da79c8a666dcc921e0a4b92fcd1e0067064bd96709abe9bd9b3b0417db0ced6013c1487abf70a562f090125cec899d65a21fbdf56c6038b29ef50677d9aec3            13378 Packages
e6ed74abfdc13ff2aea174372db146469ab0084e5d9a1faad4b9f10b3dbe7d49170b46020a575009ad13bfd2a7ef3e1488b6efb1afaa1c46e9c60cb15cc986fe             2517 Packages.gz
cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e                0 Release
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEPE3/B1HCbobUes/fqN7ZVcUKXSIFAmH6mYwACgkQqN7ZVcUK
XSIijQf/QDTjzE1T1uSTaeXMy09NOT3zZbxr69fDiBdHE8gpEaCH9V4B5xnAT0pq
7QsJ/7iFkIAhDPeoNva82fKT7zPaXdndYfwp1E6XCHjjbX4nrO5HhmzpUCMjBX3Q
vB7HcTlxr4/dNEf5giq/qUIRd25Me7KEuDbU4CESYYX4/eilRlqeoFYLmS1hfPhh
8MBqYeD9hHw8C7vyDG7oPGW0zSGn3UGMF3gxHsCo220D+Mn3rd4tnQT89EUzU3uk
LKgD84V/EnTLv9mLWlK8WKtq3gAnKL1RgvUjs6YmCWAu7WY1F48Rm7mUkaPMNqNy
rP+gTljT28H86xLsIg9LJu70Dxsukw==
=7+PA
-----END PGP SIGNATURE-----

And that's all I've got. Hopefully someone on your team sees what I'm not; it sure will be nice not to bump into that error in the terminal.

yermulnik commented 1 year ago

Same for stable repo since about yesterday:

> sudo apt update
[skip]
Err:56 https://download.wavebox.app/stable/linux/deb amd64/ InRelease
  The HTTP server sent an invalid Content-Range header Bad header data [IP: 172.67.174.148 443]
[skip]
Fetched 37,3 kB in 36s (1.039 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
6 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Failed to fetch https://download.wavebox.app/stable/linux/deb/amd64/InRelease  The HTTP server sent an invalid Content-Range header Bad header data [IP: 172.67.174.148 443]
W: Some index files failed to download. They have been ignored, or old ones used instead.

The other ipv4 104.21.40.22 has the same issue.

yermulnik commented 1 year ago

Nevermind, apt clean (apt-get clean) fixed the issue.

Thomas101 commented 1 year ago

Sometimes apt caches headers for some reason. It sounds like you ran into this. Thanks for letting me know you managed to get it working 👍

wavebox / waveboxapp

Linux APT repository serving bad header data #1372