public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: overseers@gcc.gnu.org
Subject: Re: Permanently redirecting to https (instead of temporarily)
Date: Thu, 23 Apr 2015 15:07:00 -0000	[thread overview]
Message-ID: <20150423150714.GB10477@redhat.com> (raw)
In-Reply-To: <alpine.LSU.2.20.1504192216310.3004@tuna.site>

Hi -

> The server replies with status code "307 Temporary Redirect" and
> redirects to HTTPS version ("Location:
> https://gcc.gnu.org/bugs/segfault.html"). [...]
>
> Though it's strange. Why not "301 Moved Permanently"?...

I'm afraid I don't see that particular redirect, so can't explain it
or correct it.  There -is- a redirect in place for the favicon.ico
file, to get web browsers to get it via https, and thence the HSTS
header that will let them fetch everything else with https.  But
no redirect from ordinary http: files AFAIK.

- FChE

      reply	other threads:[~2015-04-23 15:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-19 20:27 Gerald Pfeifer
2015-04-23 15:07 ` Frank Ch. Eigler [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=20150423150714.GB10477@redhat.com \
    --to=fche@redhat.com \
    --cc=gerald@pfeifer.com \
    --cc=overseers@gcc.gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).