search

OBOFoundry / purl.obolibrary.org

A system for managing OBO PURLs
BSD 3-Clause "New" or "Revised" License
75 stars 128 forks source link

some unresolved purls don't give 404s #316

Open alanruttenberg opened 7 years ago

alanruttenberg commented 7 years ago

For example I just tried purl.obolibrary.org/obo/2017-03-24/iao.owl which hasn't hit the server yet and was directed to http://ontologies.berkeleybop.org/ which has a page of XML starting with: 

<ListBucketResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<Name>bbop-ontologies</Name>
<Prefix/>
<Marker/>
<MaxKeys>1000</MaxKeys>
<IsTruncated>true</IsTruncated>
<Contents>
<Key>aeo.obo</Key>
<LastModified>2016-11-24T23:12:24.000Z</LastModified>
<ETag>"f7a6a0717bd7ede5af05c87c4640e8f3"</ETag>
alanruttenberg commented 7 years ago

Typo - won't hit the server bc wrong PURL. But nonetheless illustrates a problem. Should be purl.obolibrary.org/obo/iao/2017-03-24/iao.owl, which does work.

jamesaoverton commented 7 years ago

I can confirm that the proper PURL is working, and that the incorrect one is going to http://ontologies.berkeleybop.org/ (which looks like an Amazon S3 bucket).

We know that we don't handle failures as well as we should. See #259 and #251.

cmungall commented 7 years ago 
$ wget purl.obolibrary.org/obo/2017-03-24/iao.owl
--2017-03-24 13:28:06--  http://purl.obolibrary.org/obo/2017-03-24/iao.owl
Resolving purl.obolibrary.org (purl.obolibrary.org)... 52.3.123.63
Connecting to purl.obolibrary.org (purl.obolibrary.org)|52.3.123.63|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://purl.oclc.org/obo/2017-03-24/iao.owl [following]
--2017-03-24 13:28:06--  http://purl.oclc.org/obo/2017-03-24/iao.owl
Resolving purl.oclc.org (purl.oclc.org)... 207.241.224.2
Connecting to purl.oclc.org (purl.oclc.org)|207.241.224.2|:80... connected.
HTTP request sent, awaiting response... 302 FOUND
Location: http://www.berkeleybop.org/ontologies/2017-03-24/iao.owl [following]
--2017-03-24 13:28:06--  http://www.berkeleybop.org/ontologies/2017-03-24/iao.owl
Resolving www.berkeleybop.org (www.berkeleybop.org)... 131.243.193.109
Connecting to www.berkeleybop.org (www.berkeleybop.org)|131.243.193.109|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://ontologies.berkeleybop.org [following]
--2017-03-24 13:28:06--  http://ontologies.berkeleybop.org/
Resolving ontologies.berkeleybop.org (ontologies.berkeleybop.org)... 54.192.117.77, 54.192.117.184, 54.192.117.251, ...
Connecting to ontologies.berkeleybop.org (ontologies.berkeleybop.org)|54.192.117.77|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/xml]
Saving to: ‘iao.owl’

looks like rather than falling back to OCLC it should just 404. I think we kept that fallback as we weren't sure we'd gotten everything across.

cmungall commented 6 years ago

I think we can get rid of the OCLC fallback now, which should give the desired effect