Though perhaps surprising, that is currently how the TDS works. It uses
the services listed in the configuration catalogs to know which data
access methods to advertise. It has never used that information to
restrict the data access methods supported for a particular dataset.
This behavior has always seemed a bit unusual to me but it has never
been a high priority to change. I've added this as an issue in our
On 7/20/2010 1:08 AM, Pauline Mak wrote:
> Hi all,
> I've configured a service with the following services:
> <service name="all" base="" serviceType="compound">
> <service name="odap" serviceType="OpenDAP" base="/thredds/dodsC/" />
> <service name="wcs" serviceType="WCS" base="/thredds/wcs/" />
> <service name="wms" serviceType="WMS" base="/thredds/wms/" />
> <service name="ncss" serviceType="NetcdfSubset"
> base="/thredds/ncss/" />
> And configured in a datasetScan:
> <datasetScan name="Test all files in a directory" ID="testDatasetScan"
> path="testAll" location="content/testdata">
> <metadata inherited="true">
> I then browse to the appropriate directory in my browser and find the
> following links:
> 1. OPENDAP: /thredds/dodsC/testAll/2004050412_eta_211.nc
> 2. WCS: /thredds/wcs/testAll/2004050412_eta_211.nc
> 3. WMS: /thredds/wms/testAll/2004050412_eta_211.nc
> 4. NetcdfSubset: /thredds/ncss/testAll/2004050412_eta_211.nc
> This looks fine... however, I can also handcraft a fileServer URL like so:
> http://localhost:8080/thredds/fileServ er/testAll/2004050412_eta_211.nc
> And download the file. Is that the correct behaviour? I would think
> that since the dataset hasn't been configured to use fileServer, then
> the above link should not work...
> I'm using 4.2.20100707.0012, but also got a similar result using (a
> really old version!) TDS 4.0.36 too.