public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: "Ward, David - 0665 - MITLL" <david.ward@ll.mit.edu>
Cc: "overseers@gcc.gnu.org" <overseers@gcc.gnu.org>
Subject: Re: HTTP 403 when accessing gcc.gnu.org from MIT Lincoln Laboratory
Date: Thu, 28 Jan 2016 21:31:00 -0000	[thread overview]
Message-ID: <20160128213129.GA28186@redhat.com> (raw)
In-Reply-To: <56AA85A0.5060608@ll.mit.edu>

Hi -

> Hi, it seems that gcc.gnu.org is actively blocking any HTTP traffic from 
> MIT Lincoln Laboratory, which all originates from our proxy server, 
> llproxy.ll.mit.edu (129.55.200.20). [...]


That subnet was blacklisted for other functions on gcc.gnu.org
since 2004 for some sort of perceived and forgotten offence.
The http block is now removed.  Enjoy.

- FChE

      reply	other threads:[~2016-01-28 21:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <09F9E503E5ECBD448DAB6DB31DDF9587EB0284@LLE2K10-MBX01.mitll.ad.local>
2016-01-28 21:18 ` Ward, David - 0665 - MITLL
2016-01-28 21:31   ` 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=20160128213129.GA28186@redhat.com \
    --to=fche@redhat.com \
    --cc=david.ward@ll.mit.edu \
    --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).