Byte range support fails on noaa-goes16 S3 Bucket

[dopplershift]

As noted on conda-forge/libnetcdf-feedstock#166, the following URL https://noaa-goes16.s3.amazonaws.com/ABI-L1b-RadC/2017/059/03/OR_ABI-L1b-RadC-M3C13_G16_s20170590337505_e20170590340289_c20170590340316.nc#mode=bytes fails when trying to use ncdump -h or netcdf4-python's Dataset class with:

ncdump: https://noaa-goes16.s3.amazonaws.com/ABI-L1b-RadC/2017/059/03/OR_ABI-L1b-RadC-M3C13_G16_s20170590337505_e20170590340289_c20170590340316.nc#mode=bytes: NetCDF: Malformed URL

Adjusting it to https://noaa-goes16.s3.us-east-1.amazonaws.com/ABI-L1b-RadC/2017/059/03/OR_ABI-L1b-RadC-M3C13_G16_s20170590337505_e20170590340289_c20170590340316.nc#mode=bytes fixes the problem, but this should not be necessary based on the AWS S3 docs on supported endpoints for the us-east-1 region.

I'll also note that the URL in question comes from netcdf-c's own tst_byterange.c:

netcdf-c/nc_test/tst_byterange.c

Lines 32 to 41 in 00a722b

	struct TESTURLS {
	int format; /* instance of NC_FORMATX_XXX */
	const char* url;
	} testurls[] = {
	{NC_FORMAT_CLASSIC,"https://remotetest.unidata.ucar.edu/thredds/fileServer/testdata/2004050300_eta_211.nc#bytes"},
	#ifdef USE_HDF5
	{NC_FORMAT_NETCDF4,"https://noaa-goes16.s3.amazonaws.com/ABI-L1b-RadC/2017/059/03/OR_ABI-L1b-RadC-M3C13_G16_s20170590337505_e20170590340289_c20170590340316.nc#mode=bytes"},
	#endif
	{0,NULL}
	};

Before any work is done to correct the URL parsing/checking, that test has to be investigated to identify why it's not already failing.

[DennisHeimbigner]

Fixed by PR #2649

[zklaus]

Should this and its sister issue #2643 be closed following #2649?