From: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
To: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
Cc: overseers@gcc.gnu.org
Subject: Re: Can't access GCC's git mirror over https:// or http://
Date: Tue, 26 Nov 2019 12:55:00 -0000 [thread overview]
Message-ID: <A9E8F93A-FD74-44D8-BF01-FA60B59B719A@linaro.org> (raw)
In-Reply-To: <20191126124053.GA15059@cgf.cx>
> On Nov 26, 2019, at 3:40 PM, Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org> wrote:
>
> On Tue, Nov 26, 2019 at 11:21:38AM +0300, Maxim Kuvyrkov wrote:
>>
>> Access to GCC's git repo over https:// is broken
>> ===
>> $ git clone https://gcc.gnu.org/git/gcc.git/ gcc-bad
>> Cloning into 'gcc-bad'...
>> fatal: unable to access 'https://gcc.gnu.org/git/gcc.git/': The requested URL returned error: 403
>> ===
>>
>> My logs suggest that this broke around October 31, 2019. Git read-only access works as expected via git://gcc.gnu.org/git/gcc.git/ .
>>
>> Would you please investigate? We provide https:// access for the benefit of those behind firewalls.
>
> What is the IP address that's trying to access git? Can you access
> https://gcc.gnu.org?
>
Hi Christopher,
I can't access from 51.148.40.55 (Cambridge, UK) -- employer's network. Accessing https://gcc.gnu.org returns 403 as well.
I can access both URLs from colo machine in Germany and home machine in Moscow, Russia.
--
Maxim Kuvyrkov
https://www.linaro.org
next prev parent reply other threads:[~2019-11-26 12:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 8:21 Maxim Kuvyrkov
2019-11-26 12:40 ` Christopher Faylor
2019-11-26 12:55 ` Maxim Kuvyrkov [this message]
2019-11-26 14:45 ` Christopher Faylor
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=A9E8F93A-FD74-44D8-BF01-FA60B59B719A@linaro.org \
--to=maxim.kuvyrkov@linaro.org \
--cc=cgf-use-the-mailinglist-please@sourceware.org \
--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).