From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 73672 invoked by alias); 23 Apr 2015 15:07:23 -0000 Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org Received: (qmail 73652 invoked by uid 89); 23 Apr 2015 15:07:23 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.6 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Thu, 23 Apr 2015 15:07:21 +0000 Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t3NF7IxZ023707 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Thu, 23 Apr 2015 11:07:19 -0400 Received: from fche.csb (vpn-224-175.phx2.redhat.com [10.3.224.175]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t3NF7IaO026368; Thu, 23 Apr 2015 11:07:18 -0400 Received: by fche.csb (Postfix, from userid 2569) id 5AD2C5853F; Thu, 23 Apr 2015 11:07:14 -0400 (EDT) Date: Thu, 23 Apr 2015 15:07:00 -0000 From: "Frank Ch. Eigler" To: Gerald Pfeifer Cc: overseers@gcc.gnu.org Subject: Re: Permanently redirecting to https (instead of temporarily) Message-ID: <20150423150714.GB10477@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i X-SW-Source: 2015-q2/txt/msg00019.txt.bz2 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