[Esip-cor] [EXTERNAL] Re: cloudflare

[Annie Burgess]

Making sure we get both of David's email addresses here.

I'll take it on myself that ESIP should have given some lead time and
testing before switching to cloudflare. That said, I was assured that the
switch would not impact any of our .esipfed.org sites, so I put this in the
realm of very unintended consequences. That said, I certainly don't excuse
myself for not alerting and allowing testing.

All this to say, I've heard your feedback and will ensure future
infrastructure changes before adoption.

Annie Burgess, PhD

Lab Director | Earth Science Information Partners (ESIP)

*esipfed.org/lab <http://esipfed.org/lab>* | 585.738.7549

*Sign up for the monthly ESIP Lab update here <http://eepurl.com/dtKL8z>.*






On Tue, Aug 27, 2019 at 7:03 PM Mcgibbney, Lewis J (398M) <
lewis.j.mcgibbney at jpl.nasa.gov> wrote:

> Thanks Carlos, let’s hear back from David. We can then decide how to move
> forward.
>
> This was not an issue before ESIP started using Cloudflare.
> I understand the move to use Cloudflare but it would be nice if production
> services such as COR could be considered the next time ESIP acts on a
> significant infrastructure level change like this.
>
> Thanks
> Lewis
>
> Sent from my iPhone
>
> On Aug 27, 2019, at 16:06, Carlos Rueda via Esip-cor <
> esip-cor at lists.esipfed.org> wrote:
>
> Hi all,
>
> Here's my take:
>
> - Underlying libraries that power the COR make HTTP requests that include
> the header 'User-Agent: Java/1.8'.
> - Because of this header, Cloudflare blocks these requests.
> - this affects many parts of the functionality in the COR, making it
> almost unusable
> - Strictly speaking, IMO, this not an issue with Cloudflare nor with Java8
> - but the fact that "bots" out there have also used java8 for making
> malicious/repeated requests against a variety of sites (btw, probably,
> never to COR) has prompted ISP providers or middlewares like Cloudflare to
> just start blocking such requests
>
> Some possible solutions, not necessary mutually exclusive:
> - if easy, non-critical (I'm not sure), disable cloudflare, at least
> temporarily (while some of the folllwing can also be advanced)
> - Adjust relevant parts in the code to set an explicit, proper user-agent
> header (some parts already updated are now working again).  Not sure when
> this all can be completed because the change is trickier when they are
> behind other libraries and, unfortunately, my time is very limited.
>
> thanks,
> Carlos
>
>
> On Tue, Aug 27, 2019 at 2:12 PM Annie Burgess via Esip-cor <
> esip-cor at lists.esipfed.org> wrote:
>
>> Please reply to this email as it has the corrected email for David.
>>
>> Annie Burgess, PhD
>>
>> Lab Director | Earth Science Information Partners (ESIP)
>>
>> *esipfed.org/lab <http://esipfed.org/lab>* | 585.738.7549
>>
>> *Sign up for the monthly ESIP Lab update here <http://eepurl.com/dtKL8z>.*
>>
>>
>>
>>
>>
>>
>> On Tue, Aug 27, 2019 at 1:57 PM Annie Burgess <annieburgess at esipfed.org>
>> wrote:
>>
>>> Hey David,
>>>
>>> The ESIP Community Ontology Repository (cor.esipfed.org) is having some
>>> issues with CloudFlare. They can describe the issue - this email is just to
>>> connect you all!
>>>
>>> AB
>>>
>>> Annie Burgess, PhD
>>>
>>> Lab Director | Earth Science Information Partners (ESIP)
>>>
>>> *esipfed.org/lab <http://esipfed.org/lab>* | 585.738.7549
>>>
>>> *Sign up for the monthly ESIP Lab update here
>>> <http://eepurl.com/dtKL8z>.*
>>>
>>>
>>>
>>>
>>> _______________________________________________
>> Esip-cor mailing list
>> Esip-cor at lists.esipfed.org
>> https://lists.esipfed.org/mailman/listinfo/esip-cor
>>
> _______________________________________________
> Esip-cor mailing list
> Esip-cor at lists.esipfed.org
> https://lists.esipfed.org/mailman/listinfo/esip-cor
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.esipfed.org/pipermail/esip-cor/attachments/20190828/e8ea4e4a/attachment.htm>