Open cet900 opened 7 years ago
Wow, I don't think that's how it is supposed to work at all! Thanks for the report. I was able to reproduce this quite easily using the default catalogs we use the first time the TDS is started. I'll take a look and see what is going wrong.
Catalog-level service specifications are currently not respected. We want to enable a superset of services in TDS (server-wide) which we can pick and choose from at catalog level. However, unlisted service endpoints still result in a server response, eg: http://dap-wms.nci.org.au/thredds/catalog/rr2/National_Coverages/IR_gravity_anomaly_Australia_V1/catalog.html?dataset=rr2-NatCov/IR_gravity_anomaly_Australia_V1/IR_gravity_anomaly_Australia_V1.nc lists only two protocols: WMS and WCS.
But the following link triggers an HTTPServer download: http://dap-wms.nci.org.au/thredds/fileServer/rr2/National_Coverages/IR_gravity_anomaly_Australia_V1/IR_gravity_anomaly_Australia_V1.nc presumably because the server itself does not have this protocol disabled (nor indeed do we want to, other catalogs do require the HTTPServer facility).
Tested with: TDS4.6.6, 4.6.8 Applies to all protocols, not just HTTP.
Thanks!