[Geoserver-users] GeoServer 2.23.6 released

The GeoServer team is sharing GeoServer 2.23.6 a small update to address CVE-2024-36401 for production systems that have not yet been upgraded. This release is provided as a temporary measure for your imm

[Geoserver-users] GeoServer 2.25.2 released

The GeoServer team is pleased to share the unexpected release of GeoServer 2.25.2 . This unscheduled release is made to address 2024-36401 (the details of which will be disclosed at the end of the month).

Re: [Geoserver-users] WMS broken after GeoServer Update (SAXException)

This is great troubleshooting; please open a bug report so the information is not lost and can be fixed. We often get chats like this where workarounds are established, and then with no bug report people assume it is a well known problem (or that the developers know about it...) We do not know the

[Geoserver-users] GeoServer 2.24.4 released

*The GeoServer team is pleased to share the release of GeoServer 2.24.4 .Check out the announcement for details: - Security Considerations (please note, some are Critical)- Demo Requests page rewrittenThis

Re: [Geoserver-users] WMS broken after GeoServer Update (SAXException)

Hello everybody, i also encountered those errors when upgrading from 2.20.4 to 2.25.0 From my observations the error occurs when using extensions that contain the xercesImpl-*.jar library, like Printing or GeoFence. The error can very easily be reproduced by running the official docker image pl

Re: [Geoserver-users] WMS broken after GeoServer Update (SAXException)

Hi Moritz, for me the error is gone in 2.25.1, so please try updating. Regards Daniel From: Maneke, Moritz Sent: Dienstag, 18. Juni 2024 08:36 To: Jody Garnett ; Calliess Daniel Ing. Cc: geoserver-users Subject: [EXTERN!]: AW: [Geoserver-users] WMS broken after GeoServer Update (SAXExceptio

Re: [Geoserver-users] [EXTERN!]: Re: WMS broken after GeoServer Update (SAXException)

Hi Jody, I only "found" the ENTITY_RESOLUTION_ALLOWLIST setting while searching for a fix of the error described at the beginning of this message thread. It might be that I missed reading the change logs at some point in time before. The documentation is good so I didn't have problems understan