Bug#1080379: Wrong content type

[Mattias Wadenstein]

Package: www.debian.org
For example these files are served as 'application/x-iso9660-image' when
they should be 'text/plain'.
https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/
debian-live-12.7.0-amd64-cinnamon.iso.contents
https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/
debian-live-12.7.0-amd64-cinnamon.iso.packages

==========================================
wget -vv
https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/debian-live-12.7.0-amd64-cinnamon.iso.contents
--2024-11-07 23:46:39--
https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/debian-live-12.7.0-amd64-cinnamon.iso.contents
Resolving cdimage.debian.org (cdimage.debian.org)... 194.71.11.163,
194.71.11.173, 2001:6b0:19::163, ...
Connecting to cdimage.debian.org (cdimage.debian.org)|194.71.11.163|:443...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 52886 (52K) [application/x-iso9660-image]
Saving to: ‘debian-live-12.7.0-amd64-cinnamon.iso.contents’
debian-live-12.7.0-amd64-cinn
100%[=================================================>] 51.65K 264KB/s
in 0.2s
2024-11-07 23:46:40 (264 KB/s) -
‘debian-live-12.7.0-amd64-cinnamon.iso.contents’ saved [52886/52886]
=======================================
This is obviously a bug with cdimage.debian.org website. Reassigning this bug
report accordingly.

This should be fixed now, except for older files which have cached
metadata still out on our delivery nodes:

viterskalet:~> HEAD https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/debian-live-12.8.0-amd64-gnome.iso.contents
|grep Content-Type
Content-Type: text/plain

/Mattias Wadenstein

[Debian Bug Tracking System]

Your message dated Thu, 14 Nov 2024 17:05:51 -0500
with message-id <9024696c-e128-416f-b362-***@debian.org>
and subject line Re: Bug#1080379: Wrong content type
has caused the Debian Bug report #1080379,
regarding Wrong content type
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)