Search Mailing List Archives

Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[bioontology-support] How to report a bug?

Ray Fergerson ray.fergerson at
Tue Jun 10 15:41:03 PDT 2014

This appears to be fixed now. All links below return the appropriate class.

Note that if you make the calls in your browser with the API key then the 
browser will remember the API key on subsequent calls (in a cookie). This 
may explain why the calls appear to work with no API key. It will keep 
working for about 2 weeks. Of course outside the browser you need to provide 
the key on all calls.


From: bioontology-support 
[mailto:bioontology-support-bounces at] On Behalf Of David 
Sent: Wednesday, June 4, 2014 1:19 PM
To: support at
Subject: [bioontology-support] How to report a bug?

I am experiencing some strange behavior. Without having authenticated/passed 
in an apikey with a previous request, I make a request to:

HTTP Response: 401. This is expected. Now, I add my apikey to the end, in my 

HTTP Response: 404. Ok, perhaps I am hitting a concept that has been retired 
from the NDFRT ontology.

However, when I hit the original url again:

HTTP Response: 200, with my expected content. However, adding the apikey 
back on:

HTTP Response: 404.

Should I report this as a bug somewhere?

Kind regards,


David Park
(m) +1.317.270.4287
daviddpark at gmail dot com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the bioontology-support mailing list