unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Thomas C Kosvic <tckosvic@ix.netcom.com>, gnu@gnu.org
Cc: 55933@debbugs.gnu.org
Subject: bug#55933: Fails download of quix 1.3 virtual machine
Date: Sun, 12 Jun 2022 23:14:29 +0200	[thread overview]
Message-ID: <87pmjdefu6@nckx> (raw)
In-Reply-To: <a8b7dd92-bca2-fc60-7063-8fcf5b2e3940@ix.netcom.com>

[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]

Thomas,

Thanks for the report.  I'm CC'ing <gnu@gnu.org> as documented 
here[0] to get their opinion.

Thomas C Kosvic 写道:
> [0] does not download a file, it tries to open the file in 
> thevrowser.

This is not universal: it works fine in Firefox 100.

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.

Kind regards,

T G-R

[0]: 
https://ftp.gnu.org/gnu/guix/guix-system-vm-image-1.3.0.x86_64-linux.qcow2
[1]: https://ftp.gnu.org/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

      reply	other threads:[~2022-06-12 21:24 UTC|newest]

Thread overview: 2+ 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 [this message]

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pmjdefu6@nckx \
    --to=bug-guix@gnu.org \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).