You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A number of ontologies redirect to ftp servers. FTP doesn't play nice with HTTP caches, since it doesn't handle HEAD, or Etags. Not the end of the world, but still enough, I think, to recommend serving over HTTP.
Currently only 3 ontologies serve over FTP: PRO, ChEBI, and RS (Rat Strain).
I've already requested that PRO switch to HTTP, and will probably make a request that ChEBI do the same. I'm not familiar with RS developers, but there's a contact listed, and I don't mind asking them as well.
The text was updated successfully, but these errors were encountered:
I agree that this is a good recommendation. Caches, HEAD, and Etags are especially useful for large ontologies with frequent releases such as PRO and ChEBI.
I would opt for making a per-ontology ticket and referring to that in your email communication perhaps cc-ing obo-operations, but whatever you feel is expedient
A number of ontologies redirect to ftp servers. FTP doesn't play nice with HTTP caches, since it doesn't handle HEAD, or Etags. Not the end of the world, but still enough, I think, to recommend serving over HTTP.
Currently only 3 ontologies serve over FTP: PRO, ChEBI, and RS (Rat Strain).
I've already requested that PRO switch to HTTP, and will probably make a request that ChEBI do the same. I'm not familiar with RS developers, but there's a contact listed, and I don't mind asking them as well.
The text was updated successfully, but these errors were encountered: