Fails download of quix 1.3 virtual machine

  • Open
  • quality assurance status badge
Details
3 participants
  • Tobias Geerinckx-Rice
  • Thomas C Kosvic
  • Simon Tournier
Owner
unassigned
Submitted by
Thomas C Kosvic
Severity
normal
T
T
Thomas C Kosvic wrote on 12 Jun 2022 21:16
(address . bug-guix@gnu.org)
a8b7dd92-bca2-fc60-7063-8fcf5b2e3940@ix.netcom.com
Clicking on the down load option from the software download page:


GNU Guix 1.3.0 QEMU Image

QCOW2 virtual machine (VM) image.


Does not download a file, it tries to open the file in thevrowser. The
iso file from the other option downloads fine.

Have a look

tom kosvic
Attachment: file
T
T
Tobias Geerinckx-Rice wrote on 12 Jun 2022 23:14
87pmjdefu6@nckx
Thomas,

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

Thomas C Kosvic ???
Toggle quote (3 lines)
> [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
|
grep Content-Type
X-Content-Type-Options: nosniff
Content-Type: application/x-iso9660-image

~ λ curl -LI
|
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]:
-----BEGIN PGP SIGNATURE-----

iIMEARYKACsWIQT12iAyS4c9C3o4dnINsP+IT1VteQUCYqZZUg0cbWVAdG9iaWFz
LmdyAAoJEA2w/4hPVW15xgkBAOSQ6p7gn+sLiz6AJbTb67SLokVjtpqrkUdRDO29
K/foAQDg2rnJ166JCKp7qXmFKQcFSGlGre8MWg3E/mXyIpEHCg==
=zCsO
-----END PGP SIGNATURE-----

S
S
Simon Tournier wrote on 10 Sep 18:05 +0200
(name . Tobias Geerinckx-Rice)(address . me@tobias.gr)
87y13za3zf.fsf@gmail.com
Hi,

Very late… Well hunting old bugs. :-)

On Sun, 12 Jun 2022 at 23:14, Tobias Geerinckx-Rice <me@tobias.gr> wrote:

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

[...]

Toggle quote (17 lines)
> 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:

Toggle snippet (4 lines)
$ 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

Does it mean the issue is gone?

Cheers,
simon
T
T
Tobias Geerinckx-Rice wrote on 11 Sep 23:13 +0200
6FAEF87B-0C5C-4071-BCE4-C076DD88E65E@tobias.gr
Hi Simon,

Thanks for hunting.

On 10 September 2024 16:05:40 UTC, Simon Tournier <zimon.toutoune@gmail.com> wrote:
Toggle quote (9 lines)
>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?

Nope.

I mean, if the server were now "actively* serving a gigabyte-plus VM image as HTML, the issue would be much worse...

However, it's serving HTML because that URL is now a 404 status page. The qcow2 image has been deleted.

I'm a bit surprised by that. I somewhat assumed that releases were kept forever.

Anyway, the original issue is unchanged:

X-Content-Type-Options: nosniff

Kind regards,

T G-R

Sent on the go. Excuse or enjoy my brevity.
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 55933@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 55933
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch