Hi List
We’ve identified a potential conflict/issue in GeoNetwork 4.2.x. GeoNetwork is behind nginx, and also behind a loadbalancer and we don’t expose a port in the URL. So our settings are:
Protocol: https
Port: blank
This was causing an error when signing out of GeoNetwork, which we traced to https://github.com/GeoCat/core-geonetwork/blob/main/core/src/main/java/jeeves/config/springutil/JeevesNodeAwareLogoutSuccessHandler.java#L85-L87
Adding a port back into the settings prevents this error, even though we’re using the same URL without a port in it as before, but it then causes errors in a number of other parts of the site. In particular it breaks the ogc-api endpoint. Once you have accessed the default endpoint at https://{url-without-port}/geonetwork/api/collections then the links on the page, such as to /collections/main use the url, protocol and port from the settings, which in our case are then wrong and trigger a 400 error. Manually editing the URL to remove the port works just fine. I’m sure there are other places where this will also happen.
I know I can get around this by configuring the loadbalancer and nginx, but this seems like a compromise, and it should not be necessary to include a port in the settings unless you really need it.
Does anyone have any thoughts as to how to get around this?
Thanks
Jo
···
Jo Cook
t:+44 7930 524 155 | twitter:@archaeogeek | mastodon:@archaeogeek@anonymised.com.
Please note that currently I do not work on Friday afternoons. For urgent responses at that time, please visit support.astuntechnology.com or phone our office on 01372 744009