From: Simon Tournier <zimon.toutoune@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: gnu@gnu.org, 55933@debbugs.gnu.org,
Thomas C Kosvic <tckosvic@ix.netcom.com>
Subject: bug#55933: Fails download of quix 1.3 virtual machine
Date: Tue, 10 Sep 2024 18:05:40 +0200 [thread overview]
Message-ID: <87y13za3zf.fsf@gmail.com> (raw)
In-Reply-To: <87pmjdefu6@nckx> (Tobias Geerinckx-Rice's message of "Sun, 12 Jun 2022 23:14:29 +0200")
Hi,
Very late… Well hunting old bugs. :-)
On Sun, 12 Jun 2022 at 23:14, Tobias Geerinckx-Rice <me@tobias.gr> wrote:
> Thanks for the report. I'm CC'ing <gnu@gnu.org> as documented here[0] to get
> their opinion.
[...]
> However, there does seem to be an inconsistency with the GNU FTP server:
>
> ~ λ curl -LI
> https://ftp.gnu.org/gnu/guix/guix-system-install-1.3.0.x86_64-linux.iso |
> grep Content-Type
> X-Content-Type-Options: nosniff
> Content-Type: application/x-iso9660-image
>
> ~ λ curl -LI
> https://ftp.gnu.org/gnu/guix/guix-system-vm-image-1.3.0.x86_64-linux.qcow2 |
> grep Content-Type
> X-Content-Type-Options: nosniff
>
> The QCOW2 response is missing a Content-Type, whilst asking browsers not to
> sniff it for themselves. Apparently your browser is making an exceptionally
> bad call.
I get:
--8<---------------cut here---------------start------------->8---
$ curl -LI https://ftp.gnu.org/gnu/guix/guix-system-install-1.3.0.x86_64-linux.qcow2 | grep Content-Type
Content-Type: text/html; charset=iso-8859-1
--8<---------------cut here---------------end--------------->8---
Does it mean the issue is gone?
Cheers,
simon
next prev parent reply other threads:[~2024-09-10 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-12 19:16 bug#55933: Fails download of quix 1.3 virtual machine Thomas C Kosvic
2022-06-12 21:14 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2024-09-10 16:05 ` Simon Tournier [this message]
2024-09-11 21:13 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y13za3zf.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=55933@debbugs.gnu.org \
--cc=gnu@gnu.org \
--cc=me@tobias.gr \
--cc=tckosvic@ix.netcom.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.