cloudflare prevents ontology access due to OWLAPI/Java 8

[graybeal]

Some ontologies served by the Community Ontology Repository do not seem accessible to Protege, although they can be downloaded and opened in Protege. Tickets apparently due to this problem (the first contains more technical details):

• error 403 downloading SWEET using Protege or BioPortal ESIPFed/sweet#150
• 403 error on Protege load of COR hosted ontology ESIPFed/cor#58

BioPortal was likewise not able to open the SWEET ontology (see first ticket above). The issue was tracked to an interaction with OWLAPI, its default format for requesting ontologies in Java 8, and Cloudflare's aggressive reaction to some abusive users of Java 8. Ticket is

• Can't load SWEET, getting 403 error ncbo/bioportal-project#127

Essentially, BioPortal fixed this by moving to Java 11.

We have had poor success getting Cloudflare (cloud hosting for the ESIP site) to fix this on their end, thus it will likely only work once Protege moves to Java 11, or the header is changed so that it is not including User-Agent:Java/1.8.0_40 (ref ESIPFed/sweet#150 (comment)).

[graybeal]

Cloudflare has adjusted there settings and we found Protege access to the SWEET ontology now works.