ERDDAP™ version v2.28.1 is now available!

[chris.john]

This is the main announcement to the ERDDAP™ Announcements Mailing List. This is a minor patch update on 2.28.0 and has been tested on NOAA ERD for a day (after 2 weeks of testing 2.28.0). I'm now recommending that all ERDDAP™ administrators switch to the new version.

https://github.com/ERDDAP/erddap/releases/tag/v2.28.1

We have an official ERDDAP™ Docker image available:

https://hub.docker.com/r/erddap/erddap

or through GitHub packages:

https://github.com/ERDDAP/erddap/pkgs/container/erddap

You can read about all of the changes at
https://erddap.github.io/changes.html#version-2281

With 2.28.1 we also include support for deployments on a non-standard prefix (paths other than the normal /erddap). This requires setting the X-Forwarded-Prefix. Please see our updated documentation for either Apache or Nginx for more information if this applies to you.

Given some feedback we received on the 2.28.0 release we wanted to share some information about best practice for server configuration. With the 2.28.0 release there is an important change in behavior for setups with a reverse proxy. Deployments not using a reverse proxy and (i.e. served to the public directly on ERDDAP's Tomcat port) are unaffected.

ERDDAP™ now defaults to using request headers to determine what URL to use for links back to the server. This enables a lot of complex setups to work seamlessly. However if the reverse proxy is not configured to pass the host header properly it will cause problems.The ideal solution is to configure the reverse proxy to pass the headers.

For Apache:

 ProxyPreserveHost On
  ProxyPass /erddap http://localhost:8080/erddap

For Nginx:

location / {
    proxy_set_header Host $http_host;
    proxy_pass http://localhost:8080;
  }

If that is not an option you can configure ERDDAP™ to use the host hardcoded in setup.xml for urls by adding the following to your setup.xml:<useHeadersForUrl>false</useHeadersForUrl>

This version includes security-related changes (updated libraries), so I strongly encourage you to upgrade. See the instructions at

https://erddap.github.io/docs/server-admin/deploy-update

If you have any problems, questions, or suggestions, please create an issue on GitHub or email me.

Thank you for using ERDDAP™.

Christopher John (he/him)

NOAA Appointed Technical Director of ERDDAP™

Computer and Information Systems Manager, TSPi