From: Gerald Pfeifer <gerald@pfeifer.com>
To: overseers@gcc.gnu.org
Subject: Permanently redirecting to https (instead of temporarily)
Date: Sun, 19 Apr 2015 20:27:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1504192216310.3004@tuna.site> (raw)
He has a good point. Can we make this change?
Gerald
---------- Forwarded message ----------
From: Mikhail Maltsev <maltsevm@gmail.com>
To: jimd@aptnsw.org.au, gcc@gcc.gnu.org
Date: Tue, 14 Apr 2015 10:07:57 +0300
Subject: Re: Connecting to gcc.gnu.org - keygen_fail
14.04.2015 9:28, jimd@aptnsw.org.au writes:
> Hi,
>
> If I try to browse to pages like http://gcc.gnu.org/bugs/segfault.html I get the following Mozilla alert:
>
>>
>> An error occurred during a connection to gcc.gnu.org:443. Unable to generate public/private key pair. (Error code: sec_error_keygen_fail)
>>
>
> Advice, please?
>
The server replies with status code "307 Temporary Redirect" and
redirects to HTTPS version ("Location:
https://gcc.gnu.org/bugs/segfault.html"). Recent versions of Chrome and
Firefox (well, Iceweasel actually) handle it correctly. SSL certificate
is OK.
Though it's strange. Why not "301 Moved Permanently"?...
--
Regards,
Mikhail Maltsev
next reply other threads:[~2015-04-19 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-19 20:27 Gerald Pfeifer [this message]
2015-04-23 15:07 ` Frank Ch. Eigler
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=alpine.LSU.2.20.1504192216310.3004@tuna.site \
--to=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).