qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Myles Wilson <Mellurboo@outlook.com>,
	 "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Thomas Huth <thuth@redhat.com>
Subject: Re: Please Read: Error in website redirection
Date: Mon, 9 Dec 2024 17:48:02 +0000	[thread overview]
Message-ID: <CAFEAcA-bURNUSEvCU2yMDnYB2kRZtekbh3vZRLDNPeGr2DFeSQ@mail.gmail.com> (raw)
In-Reply-To: <CAJSP0QW+ybkxDO6G0Eja4gaHvXBq5-3GmhjPJTHyngNMC=m45Q@mail.gmail.com>

On Mon, 9 Dec 2024 at 14:28, Stefan Hajnoczi <stefanha@gmail.com> wrote:
>
> On Mon, 9 Dec 2024 at 01:42, Thomas Huth <thuth@redhat.com> wrote:
> >
> > On 08/12/2024 01.17, Myles Wilson wrote:
> > > Hello,
> > > I was recently trying to download QEMU and noticed, on the landing page of
> > > https://www.qemu.org/ <https://www.qemu.org/>,//the button titled "Full list
> > > of releases"
> > > redirects to https://download.qemu.org/ <https://download.qemu.org/> which
> > > results in a *403 forbidden* error.
> > > the same issue is present throughout the whole site with any button or
> > > hyperlink to see full releases (even the one found in https://www.qemu.org/
> > > download/ <https://www.qemu.org/download/> )
> >
> > It seems to be broken for "https://download.qemu.org" but if you manually
> > add a slash at the end ("https://download.qemu.org/") it works at least for me.
> >
> > Paolo, Stefan, looks like a server misconfiguration to me, is this something
> > that could be fixed in the configs? Otherwise, I think we should update the
> > links on the website to include a slash at the end...
>
> This issue seems to be related to how the CDN server handles the HTTP
> Referer header.
>
> Paolo: Is there a GNOME GitLab project where we can raise an issue to
> ask the CDN admins to help?
>
> The 403 response occurs when I include the referrer:

The GNOME CDN sysadmins have now kindly fixed this for us.

thanks
-- PMM


      reply	other threads:[~2024-12-09 17:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-08  0:17 Please Read: Error in website redirection Myles Wilson
2024-12-09  6:42 ` Thomas Huth
2024-12-09 14:27   ` Stefan Hajnoczi
2024-12-09 17:48     ` Peter Maydell [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

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

  git send-email \
    --in-reply-to=CAFEAcA-bURNUSEvCU2yMDnYB2kRZtekbh3vZRLDNPeGr2DFeSQ@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=Mellurboo@outlook.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.com \
    --cc=thuth@redhat.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.
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 NNTP newsgroup(s).