www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoffrey Corey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-10815) Please unblock IBM Rochester addresses from website access
Date Sat, 21 Nov 2015 02:28:10 GMT

    [ https://issues.apache.org/jira/browse/INFRA-10815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15020175#comment-15020175
] 

Geoffrey Corey commented on INFRA-10815:
----------------------------------------

The original emails were flagged by our spam filters. I have added your 2 emails to our whitelist
for the time being.

You will have to re-send the email to root@apache.org in order for the original correspondence
request in INFRA-10757 to start.

As for the content of the original email sent to root@apache.org, it does not meet the criteria
laid out.

The email does not mention:
1. the source of the problem (it must be in the email, as requested)
2. The corrective action taken
3. It does not outline (to our satisfaction) the steps taken to keep the situation from happening
again.

Until those 3 requirements are met in the email to root@apache.org, the offending IPs will
remain blocked.

> Please unblock IBM Rochester addresses from website access
> ----------------------------------------------------------
>
>                 Key: INFRA-10815
>                 URL: https://issues.apache.org/jira/browse/INFRA-10815
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Website
>            Reporter: Kurt Altmann
>
> Based on IBMs discovery of source IPs that were causing JMETER access of apache.org,
  (documented in now-closed INFRA-10757) and correcting those scripts,  IBM is requesting
the revert of the block that was put in place.  It should also be noted, that it was discovered
by the same people who made the mistake - that JMETER , when downloaded from the site - came
with a DEFAULT parameter that was set to apache.org.  It was the users neglect to change that
default - which led to the traffic storm to apache.org.  You may want to consider not having
the site default be apache.org. We also sent an email to root, not knowing process to request
the revert of block. Please let me know if questions. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message