[thredds] THREDDS 4.6.0 fails to start due to Unidata http->https policy

Just a heads up/DenverCoder9 warning, it looks like due to a change in the
Unidata http->https forwarding policy that took place in the past few
weeks, THREDDS 4.6.0 is no longer able to start properly. catalog.xml
validation fails with the following error in
content/thredds/logs/catalogInit.log:

> fatalMessages= *** XML parser fatalError (1:50)= White spaces are
required between publicId and systemId.

I assume that this is because THREDDS tries to download schema files
referenced via http in catalog.xml, as discussed here:

https://www.unidata.ucar.edu/mailing_lists/archives/thredds/2017/msg00063.html

No idea why this suddenly started happening this month when that thread is
from late 2017.

AFAIK only THREDDS 4.6.0 is affected; 4.5.5 and 4.6.1 both start without
issue, as does 4.6.13. We use an embedded Tomcat with THREDDS and some test
data in some unit tests, and noticed that tests which passed weeks ago
suddenly started failing without any code or environment changes.

Obviously 4.6.0 is four years old and anyone affected should upgrade, just
wanted to put a word of warning out as it took a while to figure out what
was happening.

Best,
Shane
  • 2019 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the thredds archives: