[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[THREDDS #IPL-302893]: Thredds 5.* issues with collections and url paths

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [THREDDS #IPL-302893]: Thredds 5.* issues with collections and url paths
  • Date: Wed, 19 Oct 2022 09:26:58 -0600
Greetings!

We actually just fixed a bug last week that the incorrect context path 
"thredds" was used instead of the configured one. Could you try the latest 
snapshot and see if that fixes your problem? You can download it here:

https://downloads.unidata.ucar.edu/tds/5.5/thredds-5.5-SNAPSHOT.war

Best,
Tara

Posted on: 20221019.0853 MDT
================================================================
We have 3 different tds servers, and we noticed that after the upgrade from
4 to 5 the url autogenerated content path for the feature collections is
defaulting to /thredds regardless that this is not the correct base path,
for example is the war is thredds2 and the web.xml and even tds properties
file have been updated. The catalog still shows the url of any collection
with the /thredds path instead of /thredds2… but if i manually type it on
the browser I can see the aggregations working correclty






Ticket Details
===================
Ticket ID: IPL-302893
Department: Support THREDDS
Priority: Normal
Status: Open
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.