Incorrect Content-Type header for .tar.xz and .tar.gz files on static.rust-lang.org
Open
Nobody has claimed this yet.
C-bug
needs-triage
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Cmd
curl -L -I https://static.rust-lang.org/dist/rust-1.97.1-x86_64-unknown-linux-gnu.tar.xz
Result
x-amz-id-2: 5p1cXcXxPqCAvGCUeKgaKzOX3Z5WO1fbDyb82wGUDwTLk6zhDfH30bSeOXS8ddbY9VPwKJ3JdJE=
x-amz-request-id: 4H897D0JJDD9FEZW
last-modified: Thu, 16 Jul 2026 12:27:40 GMT
etag: "47c4cb5deda281364582ea76efaa113d-24"
x-amz-storage-class: INTELLIGENT_TIERING
x-amz-server-side-encryption: AES256
x-amz-version-id: jTyWilsij.RItjuQ4MeWsqGok8h0JLrM
content-type: application/x-tar
server: AmazonS3
accept-ranges: bytes
age: 41120
date: Sat, 01 Aug 2026 14:02:04 GMT
via: 1.1 varnish
x-served-by: cache-icn1450044-ICN
x-cache: HIT
x-cache-hits: 0
x-timer: S1785592925.861343,VS0,VE1
content-length: 201303968
The Content-Type should be application/x-xz or application/octet-stream.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how distribution artifacts are published and served at static.rust-lang.org, using the reported curl -L -I command and the .tar.xz URL as the entry point. Verify the metadata for both .tar.xz and .tar.gz artifacts, and consider the issue done when their responses use the intended Content-Type without affecting downloads.
Written by the indexing model from the issue text.
Assessment
- Domain
- infrastructure, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100