geoserver-devel — List now closed, join us on geoserver developer forum: https://discourse.osgeo.org/invites/7DX66egwux

Re: [Geoserver-devel] [Geowebcache-devel] Code freeze has ended

[Jody G. <jod...@gm...>]

 Thanks Ian,

There is now a blog post up "GeoServer 3 Sprint Update
<https://geoserver.org/behind%20the%20scenes/2025/11/05/gs3-update.html>"
providing some details on the work done.
- -
Jody Garnett


On Oct 25, 2025 at 06:54:59, Ian Turton <ia...@ia...> wrote:

> As the code sprint winds down here in rainy Italy we can now lift the code
> freeze on the main branches, the build server is back to running on the
> main branches and is "happy", if you notice any problems then please raise
> them on the relevant developers list. While we are sure that the tests pass
> there's no guarantee that everything is working so proceed with caution.
>
> On behalf of the PSC and sprint team I want to thank everyone for
> their patience over the last week or so and I hope that you will soon start
> to see the improvements that the updated libraries will bring to your
> dependent projects too.
>
> Ian
> _______________________________________________
> Geowebcache-devel mailing list
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geowebcache-devel
>

[Geoserver-devel] [GEOS-11926] Incompatibility between ogcapi features module and wfs

[Pierre M. <pie...@ca...>]

Hi,

I found out that having the ogcapi features plugin in the classpath was
altering the behaviour of WFS services: the WFS GetCapabilities advises an
outputFormat which actually is not available for GetFeatures operations
("application/geo+json"). I opened an issue on osgeo's JIRA  in this
regard[1], but I also had some time to dig further, and I am perplexed as
how I could fix it myself.

It seems that the RFCGeoJSONGeaturesResponse implements the
canHandle(Version) method from a parent class which always return true,
making it appearing into the WFS GetCapabilities. My guess was to return
false when WFS is involved and true otherwise, implementing the canHandle()
on the class the following way:

@Override public boolean canHandle(Version version) { // Do not interfere
with WFS if (version.equals(WFSInfo.Version.V_10.getVersion()) ||
version.equals(WFSInfo.Version.V_11.getVersion()) ||
version.equals(WFSInfo.Version.V_20.getVersion())) return false; return
true; }

But it sounds quite fragile as a fix (what if a new version of OGCAPI
arises which would clash with WFS versions) ? I am not even sure if the RFC
GeoJSON class could not be actually used for WFS operations (yet it comes
with the ogcapi plugin), or if it should not be mentioned in the WFS
operations at all.

What do you think ?

Best regards,

[1] https://osgeo-org.atlassian.net/browse/GEOS-11926
-- 

Pierre Mauduit

Re: [Geoserver-devel] Serious unit testing issue: all modules with GUI run exactly 0 tests

[Niels C. <ni...@sc...>]

Hello Andrea and others,

I noticed today that on newer versions of geoserver no wicket tests are 
running any more, and found this email from last year. Are there any 
plans to run wicket tests again?

Related to this issue is that all the web tests of taskmanager community 
modules are broken. After figuring out the problem is with the 
WicketTester, I wanted to see how other wicket tests are not failing. 
Then I found out the reason is that they are not running any more at all.

Regards

Niels

On 10/8/24 15:00, Andrea Aime wrote:
> Hì all,
> Daniele just reported me some mysterious issues with the MapML module: 
> the build was running no tests at all, just passing without executing 
> a single one.
>
> We looked into it, and all modules where the new junit-jupiter (JUnit 
> 5) dependency has been added, fail to run the JUnit 4 tests. The 
> dependency has been added as part of the Wicket 9 upgrade merge, as 
> the new Wicket testing framework needs the JUnit 5 classes in the 
> classpath.
>
> The issue is that surefire picks the JUnit runner based on what's in 
> the classpath, if it finds JUnit5, it will only run JUnit5 tests.
>
> Now... I could understand if this affected a few modules that are 
> mixing in wicket dependencies, but even web-core builds with the 
> following:
>
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
>
> One way to have the Junit 4 tests to run, is to have the junit-vintage 
> engine installed, which is still part of JUnit5, but able to run 
> JUnit4 tests. I've tried on web-cor, and the result looks grim... once 
> the tests start running, there's quite a bit of failures:
>
> [ERROR] Failures:
> [ERROR] LayerGroupEditPageTest.testLayerGroupLinkWithWorkspace:299 
> path: 
> 'publishedinfo:tabs:panel:layers:popup:content:listContainer:items' 
> does not exist for page: LayerGroupEditPage
> [ERROR] LayerGroupEditPageTest.testLayerGroupStyle:722 path: 
> 'publishedinfo:tabs:panel:layerGroupStyles:listContainer:styleList:0:layerGroupStylePanel:layerGroupEntryPanel:popup:content:listContainer:items:1:itemProperties:0:component:link' 
> does not exist for page: LayerGroupEditPage
> [ERROR] LayerGroupEditPageTest.testLayerGroupStyle2:775 path: 
> 'publishedinfo:tabs:panel:layerGroupStyles:listContainer:styleList:0:layerGroupStylePanel:layerGroupEntryPanel:popup:content:listContainer:items:3:itemProperties:0:component:link' 
> does not exist for page: LayerGroupEditPage
> [ERROR] LayerGroupEditPageTest.testLayerGroupStyleSelection:862 path: 
> 'publishedinfo:tabs:panel:layerGroupStyles:listContainer:styleList:0:layerGroupStylePanel:layerGroupEntryPanel:popup:content:listContainer:items:2:itemProperties:0:component:link' 
> does not exist for page: LayerGroupEditPage
> [ERROR] LayerGroupEditPageTest.testLayerLink:212 path: 
> 'publishedinfo:tabs:panel:layers:popup:content:listContainer:items' 
> does not exist for page: LayerGroupEditPage
> [ERROR] LayerGroupEditPageTest.testLayerLinkWithWorkspace:265 path: 
> 'publishedinfo:tabs:panel:layers:popup:content:listContainer:items' 
> does not exist for page: LayerGroupEditPage
> [ERROR] LayerGroupEditPageTest.testStyleGroupLink:238 path: 
> 'publishedinfo:tabs:panel:layers:popup:content:listContainer:items' 
> does not exist for page: LayerGroupEditPage
> [ERROR] ResourceConfigurationPageTest.testConsistentUpdateWMTSBbox:834 
> path: 
> 'publishedinfo:tabs:panel:theList:0:content:referencingForm:nativeSRS:popup:content:table:listContainer:items:1:itemProperties:0:component:link' 
> does not exist for page: ResourceConfigurationPage
> [ERROR] ResourceConfigurationPageTest.testWFSDataStoreResource:467 
> path: 
> 'publishedinfo:tabs:panel:theList:0:content:referencingForm:nativeSRS:popup:content:table:listContainer:items:1:itemProperties:0:component:link' 
> does not exist for page: ResourceConfigurationPage
> [ERROR] ResourceConfigurationPageTest.testWMTSOtherCRS:584 path: 
> 'publishedinfo:tabs:panel:theList:0:content:referencingForm:nativeSRS:popup:content:table:listContainer:items:1:itemProperties:0:component:link' 
> does not exist for page: ResourceConfigurationPage
> [ERROR] ResourceConfigurationPageTest.testWMTSOtherCRSUrnFormat:622 
> path: 
> 'publishedinfo:tabs:panel:theList:0:content:referencingForm:nativeSRS:popup:content:table:listContainer:items' 
> does not exist for page: ResourceConfigurationPage
> [ERROR] CRSPanelTest.testPlanetaryList:245 Unable to set value. 
> Couldn't find component with name: 
> crs:popup:content:table:filterForm:filter ==> expected: not <null>
> [ERROR] CRSPanelTest.testPlanetaryPopupWindow:227 path: 
> 'form:crs:popup:content:wkt' does not exist for page: CRSPanelTestPage
> [ERROR] CRSPanelTest.testPopupWindow:69 path: 
> 'form:crs:popup:content:wkt' does not exist for page: CRSPanelTestPage
> [ERROR] Errors:
> [ERROR] GeoServerAboutPageTest.testHideSensitiveInfo:40 » 
> WicketRuntime The component(...
> [ERROR] GeoServerAboutPageTest.testLoginFormAction:21 » WicketRuntime 
> The component(s)...
> [INFO]
> [ERROR] Tests run: 405, Failures: 14, Errors: 2, Skipped: 10
> [INFO]
>
> This is just web-core... how many more are broken?
>
> I think the Wicket 9 merge should be reverted until it actually 
> builds. Opinions?
>
> Regards,
>
> Andrea Aime
>
> ==
>
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us <http://bit.ly/gs-services-us>for 
> more information.
>
> ==Ing. Andrea Aime @geowolfTechnical Lead
>
> GeoSolutions Groupphone: +39 0584 962313
>
> fax:     +39 0584 1660272
>
> mob:   +39  339 8844549
>
>
> https://www.geosolutionsgroup.com/ <https://www.geosolutionsgroup.com/>
>
> http://twitter.com/geosolutions_it <http://twitter.com/geosolutions_it>
>
> -------------------------------------------------------
>
>
> Con riferimento alla normativa sul trattamento dei dati personali 
> (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati 
> “GDPR”), si precisa che ogni circostanza inerente alla presente email 
> (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui 
> conoscenza è riservata al/i solo/i destinatario/i indicati dallo 
> scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a 
> cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato 
> se potesse darmene notizia.This email is intended only for the person 
> or entity to which it is addressed and may contain information that is 
> privileged, confidential or otherwise protected from disclosure. We 
> remind that - as provided by European Regulation 2016/679 “GDPR” - 
> copying, dissemination or use of this e-mail or the information herein 
> by anyone other than the intended recipient is prohibited. If you have 
> received this email by mistake, please notify us immediately by 
> telephone or e-mail
>
>
> _______________________________________________
> Geoserver-devel mailing list
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Proposal for a new GeoServer community module: WPS Download NetCDF format support.

[Jody G. <jod...@gm...>]

 Daniele this email list is no longer active, please send your
communication to the developer forum.
- -
Jody Garnett


On May 22, 2025 at 2:56:11 AM, Daniele Romagnoli <
dan...@ge...> wrote:

> Hi GeoServer community.
> I would like to propose a new community module to improve Raster Download
> in the WPS Download process, by supporting NetCDF output.
> https://osgeo-org.atlassian.net/browse/GEOS-11839
>
> The current WPS Download
> <https://docs.geoserver.org/main/en/user/extensions/wps-download/index.html>
> module in GeoServer supports both raster and vector data downloads. For
> raster data, it allows the extraction of a single GridCoverage2D and
> exports it to standard formats (for example, GeoTIFF) .
>
> This proposal specifically targets enhancements to the raster download
> capabilities, with a focus on better handling of SpatioTemporal
> coverages—datasets that include additional dimensions such as time,
> elevation, or other custom user-defined dimensions. A trivial example could
> be water temperature data produced by forecasting models, often delivered
> via NetCDF or ImageMosaic, with values varying across time and depth.
>
> The enhancement involves allowing users to apply dimension-based filters
> on the underlying GranuleSource. Matching granules (i.e., individual
> GridCoverage2D instances corresponding to specific dimension values) will
> be aggregated into a GranuleStack—similar to the behavior already
> implemented in WCS 2.0 when trimming across dimensions. The resulting
> GranuleStack can then be encoded into a NetCDF file, leveraging the
> existing NetCDF output functionality already available in WCS 2.0 through
> the NetCDF output extension
> <https://docs.geoserver.org/main/en/user/extensions/netcdf-out/index.html#netcdf-output-format>
> .
>
> This new functionality will be delivered as a separate community module,
> that depends on:
>  - The WPS Download module
>  - The NetCDF Output extension
>
> By structuring it this way, we ensure that NetCDF-related dependencies are
> only included when explicitly required, keeping the core WPS Download
> module lightweight.
>
>
> https://github.com/geoserver/geoserver/pull/8566
>
> Regards,
>
> Daniele Romagnoli
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Daniele Romagnoli
> Senior Software Engineer
>
> GeoSolutions Group
> phone: +39 0584 962313
> fax:      +39 0584 1660272
>
> https://www.geosolutionsgroup.com/
> http://twitter.com/geosolutions_it
> -------------------------------------------------------
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail.
> _______________________________________________
> Geoserver-devel mailing list
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>

[Geoserver-devel] Proposal for a new GeoServer community module: WPS Download NetCDF format support.

[Daniele R. <dan...@ge...>]

Hi GeoServer community.
I would like to propose a new community module to improve Raster Download
in the WPS Download process, by supporting NetCDF output.
https://osgeo-org.atlassian.net/browse/GEOS-11839

The current WPS Download
<https://docs.geoserver.org/main/en/user/extensions/wps-download/index.html>
module in GeoServer supports both raster and vector data downloads. For
raster data, it allows the extraction of a single GridCoverage2D and
exports it to standard formats (for example, GeoTIFF) .

This proposal specifically targets enhancements to the raster download
capabilities, with a focus on better handling of SpatioTemporal
coverages—datasets that include additional dimensions such as time,
elevation, or other custom user-defined dimensions. A trivial example could
be water temperature data produced by forecasting models, often delivered
via NetCDF or ImageMosaic, with values varying across time and depth.

The enhancement involves allowing users to apply dimension-based filters on
the underlying GranuleSource. Matching granules (i.e., individual
GridCoverage2D instances corresponding to specific dimension values) will
be aggregated into a GranuleStack—similar to the behavior already
implemented in WCS 2.0 when trimming across dimensions. The resulting
GranuleStack can then be encoded into a NetCDF file, leveraging the
existing NetCDF output functionality already available in WCS 2.0 through
the NetCDF output extension
<https://docs.geoserver.org/main/en/user/extensions/netcdf-out/index.html#netcdf-output-format>
.

This new functionality will be delivered as a separate community module,
that depends on:
 - The WPS Download module
 - The NetCDF Output extension

By structuring it this way, we ensure that NetCDF-related dependencies are
only included when explicitly required, keeping the core WPS Download
module lightweight.


https://github.com/geoserver/geoserver/pull/8566

Regards,

Daniele Romagnoli

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.
==

Daniele Romagnoli
Senior Software Engineer

GeoSolutions Group
phone: +39 0584 962313
fax:      +39 0584 1660272

https://www.geosolutionsgroup.com/
http://twitter.com/geosolutions_it
-------------------------------------------------------

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
precisa che ogni circostanza inerente alla presente email (il suo
contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is
addressed and may contain information that is privileged, confidential or
otherwise protected from disclosure. We remind that - as provided by
European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
e-mail or the information herein by anyone other than the intended
recipient is prohibited. If you have received this email by mistake, please
notify us immediately by telephone or e-mail.

Re: [Geoserver-devel] New community module: OGC API Processes

[Rahkonen J. <juk...@ma...>]

+1

-Jukka Rahkonen-

________________________________________
Lähettäjä: Andrea Aime
Lähetetty: Keskiviikko 30. huhtikuuta 2025 11.36
Vastaanottaja: GeoServer
Aihe: [Geoserver-devel] New community module: OGC API Processes

Hi all,I'd like to propose a new community module implementing OGC API Processes.It's going to follow the usual script, leverage the existing WPS implementation tosupport process handling, async execution, output encoding, process security,internal data access and so on.Regards,Andrea Aime==GeoServer Professional Services from the experts!Visit http://bit.ly/gs-services-us for more information.==Ing. Andrea Aime @geowolfTechnical LeadGeoSolutions Groupphone: +39 0584 962313fax:     +39 0584 1660272mob:   +39  339 8844549https://www.geosolutionsgroup.com/http://twitter.com/geosolutions_it-------------------------------------------------------Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail

Re: [Geoserver-devel] New community module: OGC API Processes

[Andrea A. <and...@ge...>]

Whoops, did not notice, thanks for pointing that out!
Message sent to discourse as well

Regards,

Andrea Aime


==


GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax:     +39 0584 1660272

mob:   +39  339 8844549

https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

-------------------------------------------------------

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
precisa che ogni circostanza inerente alla presente email (il suo
contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is
addressed and may contain information that is privileged, confidential or
otherwise protected from disclosure. We remind that - as provided by
European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
e-mail or the information herein by anyone other than the intended
recipient is prohibited. If you have received this email by mistake, please
notify us immediately by telephone or e-mail


On Wed, Apr 30, 2025 at 12:21 PM Alexandre Gacon <ale...@gm...>
wrote:

> It shouldn't be posted on Discourse now?
>
> Alexandre
>
> Le mer. 30 avr. 2025 à 12:16, Alessio Fabiani <
> ale...@ge...> a écrit :
>
>> +1
>>
>> On Wed, Apr 30, 2025 at 11:30 AM Simone Giannecchini <
>> sim...@ge...> wrote:
>>
>>> +1
>>>
>>> Regards,
>>> Simone Giannecchini
>>> ==
>>> Online training classes for GeoNode, GeoServer and MapStore from the
>>> experts!
>>> Visit https://www.geosolutionsgroup.com/professional-training/ for more
>>> information.
>>> ==
>>> Ing. Simone Giannecchini
>>> Founder/Director GeoSolutions Italy
>>> President GeoSolutions USA
>>>
>>> phone: +39 0584 962313
>>> fax:     +39 0584 1660272
>>> mob:   +39  333 8128928
>>> US: +1 (845) 547-7905
>>>
>>> https://www.geosolutionsgroup.com
>>> https://twitter.com/geosolutions_it
>>>
>>> -------------------------------------------------------
>>> This email is intended only for the person or entity to which it is
>>> addressed and may contain information that is privileged, confidential or
>>> otherwise protected from disclosure. We remind that - as provided by
>>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
>>> e-mail or the information herein by anyone other than the intended
>>> recipient is prohibited. If you have received this email by mistake, please
>>> notify us immediately by telephone or e-mail.
>>>
>>>
>>> Il giorno mer 30 apr 2025 alle 10:45 Andrea Aime <
>>> and...@ge...> ha scritto:
>>>
>>>> Hi all,
>>>> I'd like to propose a new community module implementing OGC API
>>>> Processes.
>>>> It's going to follow the usual script, leverage the existing WPS
>>>> implementation to
>>>> support process handling, async execution, output encoding, process
>>>> security,
>>>> internal data access and so on.
>>>>
>>>> Regards,
>>>>
>>>> Andrea Aime
>>>>
>>>>
>>>> ==
>>>>
>>>>
>>>> GeoServer Professional Services from the experts!
>>>>
>>>> Visit http://bit.ly/gs-services-us for more information.
>>>>
>>>> ==
>>>>
>>>> Ing. Andrea Aime
>>>> @geowolf
>>>> Technical Lead
>>>>
>>>> GeoSolutions Group
>>>> phone: +39 0584 962313
>>>>
>>>> fax:     +39 0584 1660272
>>>>
>>>> mob:   +39  339 8844549
>>>>
>>>> https://www.geosolutionsgroup.com/
>>>>
>>>> http://twitter.com/geosolutions_it
>>>>
>>>> -------------------------------------------------------
>>>>
>>>> Con riferimento alla normativa sul trattamento dei dati personali (Reg.
>>>> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
>>>> precisa che ogni circostanza inerente alla presente email (il suo
>>>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
>>>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
>>>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
>>>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>>>>
>>>> This email is intended only for the person or entity to which it is
>>>> addressed and may contain information that is privileged, confidential or
>>>> otherwise protected from disclosure. We remind that - as provided by
>>>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
>>>> e-mail or the information herein by anyone other than the intended
>>>> recipient is prohibited. If you have received this email by mistake, please
>>>> notify us immediately by telephone or e-mail
>>>> _______________________________________________
>>>> Geoserver-devel mailing list
>>>> Geo...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>>
>>> _______________________________________________
>>> Geoserver-devel mailing list
>>> Geo...@li...
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>
>>
>>
>> --
>>
>> Regards,
>>
>> Alessio Fabiani
>>
>> ==
>> GeoServer Professional Services from the experts!
>>
>> Visit http://bit.ly/gs-services-us for more information.
>> ==
>>
>> Ing. Alessio Fabiani
>>
>> @alfa7691
>> Founder/Technical Lead
>>
>>
>> GeoSolutions Group
>> phone: +39 0584 962313
>>
>> fax:     +39 0584 1660272
>>
>> mob:   +39  331 6233686
>>
>> https://www.geosolutionsgroup.com/
>>
>> http://twitter.com/geosolutions_it
>>
>> -------------------------------------------------------
>>
>> Con riferimento alla normativa sul trattamento dei dati personali (Reg.
>> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
>> precisa che ogni circostanza inerente alla presente email (il suo
>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>>
>> This email is intended only for the person or entity to which it is
>> addressed and may contain information that is privileged, confidential or
>> otherwise protected from disclosure. We remind that - as provided by
>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
>> e-mail or the information herein by anyone other than the intended
>> recipient is prohibited. If you have received this email by mistake, please
>> notify us immediately by telephone or e-mail.
>> _______________________________________________
>> Geoserver-devel mailing list
>> Geo...@li...
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>
>
> --
> Alexandre Gacon
> _______________________________________________
> Geoserver-devel mailing list
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>

Re: [Geoserver-devel] New community module: OGC API Processes

[Alexandre G. <ale...@gm...>]

It shouldn't be posted on Discourse now?

Alexandre

Le mer. 30 avr. 2025 à 12:16, Alessio Fabiani <
ale...@ge...> a écrit :

> +1
>
> On Wed, Apr 30, 2025 at 11:30 AM Simone Giannecchini <
> sim...@ge...> wrote:
>
>> +1
>>
>> Regards,
>> Simone Giannecchini
>> ==
>> Online training classes for GeoNode, GeoServer and MapStore from the
>> experts!
>> Visit https://www.geosolutionsgroup.com/professional-training/ for more
>> information.
>> ==
>> Ing. Simone Giannecchini
>> Founder/Director GeoSolutions Italy
>> President GeoSolutions USA
>>
>> phone: +39 0584 962313
>> fax:     +39 0584 1660272
>> mob:   +39  333 8128928
>> US: +1 (845) 547-7905
>>
>> https://www.geosolutionsgroup.com
>> https://twitter.com/geosolutions_it
>>
>> -------------------------------------------------------
>> This email is intended only for the person or entity to which it is
>> addressed and may contain information that is privileged, confidential or
>> otherwise protected from disclosure. We remind that - as provided by
>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
>> e-mail or the information herein by anyone other than the intended
>> recipient is prohibited. If you have received this email by mistake, please
>> notify us immediately by telephone or e-mail.
>>
>>
>> Il giorno mer 30 apr 2025 alle 10:45 Andrea Aime <
>> and...@ge...> ha scritto:
>>
>>> Hi all,
>>> I'd like to propose a new community module implementing OGC API
>>> Processes.
>>> It's going to follow the usual script, leverage the existing WPS
>>> implementation to
>>> support process handling, async execution, output encoding, process
>>> security,
>>> internal data access and so on.
>>>
>>> Regards,
>>>
>>> Andrea Aime
>>>
>>>
>>> ==
>>>
>>>
>>> GeoServer Professional Services from the experts!
>>>
>>> Visit http://bit.ly/gs-services-us for more information.
>>>
>>> ==
>>>
>>> Ing. Andrea Aime
>>> @geowolf
>>> Technical Lead
>>>
>>> GeoSolutions Group
>>> phone: +39 0584 962313
>>>
>>> fax:     +39 0584 1660272
>>>
>>> mob:   +39  339 8844549
>>>
>>> https://www.geosolutionsgroup.com/
>>>
>>> http://twitter.com/geosolutions_it
>>>
>>> -------------------------------------------------------
>>>
>>> Con riferimento alla normativa sul trattamento dei dati personali (Reg.
>>> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
>>> precisa che ogni circostanza inerente alla presente email (il suo
>>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
>>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
>>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
>>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>>>
>>> This email is intended only for the person or entity to which it is
>>> addressed and may contain information that is privileged, confidential or
>>> otherwise protected from disclosure. We remind that - as provided by
>>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
>>> e-mail or the information herein by anyone other than the intended
>>> recipient is prohibited. If you have received this email by mistake, please
>>> notify us immediately by telephone or e-mail
>>> _______________________________________________
>>> Geoserver-devel mailing list
>>> Geo...@li...
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>>
>> _______________________________________________
>> Geoserver-devel mailing list
>> Geo...@li...
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>
>
> --
>
> Regards,
>
> Alessio Fabiani
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Alessio Fabiani
>
> @alfa7691
> Founder/Technical Lead
>
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax:     +39 0584 1660272
>
> mob:   +39  331 6233686
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail.
> _______________________________________________
> Geoserver-devel mailing list
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


-- 
Alexandre Gacon

Re: [Geoserver-devel] New community module: OGC API Processes

[Alessio F. <ale...@ge...>]

+1

On Wed, Apr 30, 2025 at 11:30 AM Simone Giannecchini <
sim...@ge...> wrote:

> +1
>
> Regards,
> Simone Giannecchini
> ==
> Online training classes for GeoNode, GeoServer and MapStore from the
> experts!
> Visit https://www.geosolutionsgroup.com/professional-training/ for more
> information.
> ==
> Ing. Simone Giannecchini
> Founder/Director GeoSolutions Italy
> President GeoSolutions USA
>
> phone: +39 0584 962313
> fax:     +39 0584 1660272
> mob:   +39  333 8128928
> US: +1 (845) 547-7905
>
> https://www.geosolutionsgroup.com
> https://twitter.com/geosolutions_it
>
> -------------------------------------------------------
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail.
>
>
> Il giorno mer 30 apr 2025 alle 10:45 Andrea Aime <
> and...@ge...> ha scritto:
>
>> Hi all,
>> I'd like to propose a new community module implementing OGC API Processes.
>> It's going to follow the usual script, leverage the existing WPS
>> implementation to
>> support process handling, async execution, output encoding, process
>> security,
>> internal data access and so on.
>>
>> Regards,
>>
>> Andrea Aime
>>
>>
>> ==
>>
>>
>> GeoServer Professional Services from the experts!
>>
>> Visit http://bit.ly/gs-services-us for more information.
>>
>> ==
>>
>> Ing. Andrea Aime
>> @geowolf
>> Technical Lead
>>
>> GeoSolutions Group
>> phone: +39 0584 962313
>>
>> fax:     +39 0584 1660272
>>
>> mob:   +39  339 8844549
>>
>> https://www.geosolutionsgroup.com/
>>
>> http://twitter.com/geosolutions_it
>>
>> -------------------------------------------------------
>>
>> Con riferimento alla normativa sul trattamento dei dati personali (Reg.
>> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
>> precisa che ogni circostanza inerente alla presente email (il suo
>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>>
>> This email is intended only for the person or entity to which it is
>> addressed and may contain information that is privileged, confidential or
>> otherwise protected from disclosure. We remind that - as provided by
>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
>> e-mail or the information herein by anyone other than the intended
>> recipient is prohibited. If you have received this email by mistake, please
>> notify us immediately by telephone or e-mail
>> _______________________________________________
>> Geoserver-devel mailing list
>> Geo...@li...
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
> _______________________________________________
> Geoserver-devel mailing list
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>


-- 

Regards,

Alessio Fabiani

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.
==

Ing. Alessio Fabiani

@alfa7691
Founder/Technical Lead


GeoSolutions Group
phone: +39 0584 962313

fax:     +39 0584 1660272

mob:   +39  331 6233686

https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

-------------------------------------------------------

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
precisa che ogni circostanza inerente alla presente email (il suo
contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is
addressed and may contain information that is privileged, confidential or
otherwise protected from disclosure. We remind that - as provided by
European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
e-mail or the information herein by anyone other than the intended
recipient is prohibited. If you have received this email by mistake, please
notify us immediately by telephone or e-mail.

Re: [Geoserver-devel] New community module: OGC API Processes

[Simone G. <sim...@ge...>]

+1

Regards,
Simone Giannecchini
==
Online training classes for GeoNode, GeoServer and MapStore from the
experts!
Visit https://www.geosolutionsgroup.com/professional-training/ for more
information.
==
Ing. Simone Giannecchini
Founder/Director GeoSolutions Italy
President GeoSolutions USA

phone: +39 0584 962313
fax:     +39 0584 1660272
mob:   +39  333 8128928
US: +1 (845) 547-7905

https://www.geosolutionsgroup.com
https://twitter.com/geosolutions_it

-------------------------------------------------------
This email is intended only for the person or entity to which it is
addressed and may contain information that is privileged, confidential or
otherwise protected from disclosure. We remind that - as provided by
European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
e-mail or the information herein by anyone other than the intended
recipient is prohibited. If you have received this email by mistake, please
notify us immediately by telephone or e-mail.


Il giorno mer 30 apr 2025 alle 10:45 Andrea Aime <
and...@ge...> ha scritto:

> Hi all,
> I'd like to propose a new community module implementing OGC API Processes.
> It's going to follow the usual script, leverage the existing WPS
> implementation to
> support process handling, async execution, output encoding, process
> security,
> internal data access and so on.
>
> Regards,
>
> Andrea Aime
>
>
> ==
>
>
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
>
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax:     +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> _______________________________________________
> Geoserver-devel mailing list
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>

[Geoserver-devel] New community module: OGC API Processes

[Andrea A. <and...@ge...>]

Hi all,
I'd like to propose a new community module implementing OGC API Processes.
It's going to follow the usual script, leverage the existing WPS
implementation to
support process handling, async execution, output encoding, process
security,
internal data access and so on.

Regards,

Andrea Aime


==


GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax:     +39 0584 1660272

mob:   +39  339 8844549

https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

-------------------------------------------------------

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
precisa che ogni circostanza inerente alla presente email (il suo
contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is
addressed and may contain information that is privileged, confidential or
otherwise protected from disclosure. We remind that - as provided by
European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
e-mail or the information herein by anyone other than the intended
recipient is prohibited. If you have received this email by mistake, please
notify us immediately by telephone or e-mail

[Geoserver-devel] GeoServer 2.26.3 release manager (aka, me)

[Andrea A. <and...@ge...>]

Hi all,
I see we don't have a release manager for 2.26.3 so... I'm volunteering to
do it!
I've updated the release schedule page accordingly.

Regards,

Andrea Aime


==


GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax:     +39 0584 1660272

mob:   +39  339 8844549

https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

-------------------------------------------------------

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
precisa che ogni circostanza inerente alla presente email (il suo
contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is
addressed and may contain information that is privileged, confidential or
otherwise protected from disclosure. We remind that - as provided by
European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
e-mail or the information herein by anyone other than the intended
recipient is prohibited. If you have received this email by mistake, please
notify us immediately by telephone or e-mail

[Geoserver-devel] performance regression with [GEOS-11423] Use securityFilter in SecureCatalogImpl bulk get methods

[Niels C. <ni...@sc...>]

<div><img width="1" height="1" src='https://dficcfc.r.af.d.sendibt2.com/tr/op/Ys_K-f0b5uUlIxZ7hUTZ_YVpPnQRxKhlPt-IGmKUilSRaUoUYS6XszD0WCgz6ifk2sVDhUUxjpQxVMet28CyK-TmiP3nKFLCLUBVkO56yWvjD6Sfs-h1PTmjHY27XkwO5QeHOMEht_VT_R9icogdhi6oJNt9nwsK4JOV3RBHciVJJWwnFEcdidHtJWuEFY4vhMMaRXBEOmO_PPFmH-ravAf0nnDaaoWmDcf2Bf6MzQ' /></div>Hello Gabriel and others,<br/><br/>It seems that the changes in <br/>https://github.com/geoserver/geoserver/pull/7698 have caused a serious <br/>performance regression in certain situations.<br/><br/>In one setup, the wfs getfeature POST request has gone from <0.5 seconds <br/>to >4 seconds.<br/><br/>The setup where I observed this uses jdbcconfig with hundreds of layers <br/>and security rules (per layer). This is somewhat ironic because the  <br/>pull request was meant to improve performance with database catalogues <br/>in particular.<br/><br/>The problem is that building the security filter when you have hundreds <br/>of rules is very expensive. Rules are specified with layer names and <br/>they all have to be translated to IDs. I tried improvements to <br/>jdbcconfig in using the cache, this has reduced the time from 4 seconds <br/>to 1.5 seconds, a substantial difference but still substantially more <br/>expensive than the old version. The problem remains that building the <br/>filter is too expensive with many rules. Would it be a good idea to keep <br/>the security filter in a cache, indexed by Pair<Authentication, Class<? <br/>extends CatalogInfo> ?<br/><br/>The issue does not occur for GET requests because it does not trigger <br/>WFSXmlUtils.initWFSConfiguration which triggers getting all layers from <br/>the catalogue (secured). Is it perhaps possible to cache the WFS <br/>configuration between different requests? Is using the secured catalog <br/>even required here for parsing the XML? (I have no idea)<br/><br/>Kind Regards<br/><br/>Niels<br/><br/>

Re: [Geoserver-devel] CSP with a proxy, how to deal with it

[Humphries, G. <Gra...@st...>]

Hi Andrea,

We have recently reconfigured our Tomcat installations to use https only, so that any request via the proxy is redirected to https://<internal_server>:port/geoserver<https://%3cinternal_server%3e:port/geoserver>


This would be another configuration option

Regards,

Graham Humphries | System Analyst
Department of State Growth
4 Salamanca Place, Hobart TAS 7000 | GPO Box 536, Hobart TAS 7001
P: (03) 6166 3155
www.stategrowth.tas.gov.au<https://www.stategrowth.tas.gov.au/>
Courage to make a difference through
TEAMWORK | INTEGRITY | RESPECT | EXCELLENCE

In recognition of the deep history and culture of this island, I acknowledge and pay my respects to all Tasmanian Aboriginal people; the past, and present custodians of the Land.

From: Andrea Aime <and...@ge...>
Sent: Tuesday, 4 February 2025 1:03 AM
To: GeoServer <geo...@li...>
Subject: [Geoserver-devel] CSP with a proxy, how to deal with it

Hi all,
I've spent some time trying to figure out how to attack the issue of CSP + Proxy with SSL termination, this mail contains my findings (warning, long and technical).

First of all, what's going on?
GeoServer code, Spring security, and Wicket internals, all tend to use HTTPServletReponse.redirect("${relativePath}"), where relativePath is often "web".

>From Servlet API javadoc<https://javaee.github.io/javaee-spec/javadocs/javax/servlet/http/HttpServletResponse.html#sendRedirect-java.lang.String-> (thanks Steve) we learn the method should be implemented by the container by turning the relative path into an absolute URL.
That is done by taking the HTTP Host header, which is part of the spec and guaranteed to be there, the context path (e.g., "geoserver") and the relative path provided as an argument.

The protocol is an issue: there is not true standard HTTP header indicating the protocol (there are non-standard headers though, more on this later), so the servlet container will use whatever protocol it received the request onto.

Now, it's pretty common practice that SSL is handled by proxy in front of GeoServer, with nginx and apache being common choices. So the request goes to, say "https://gs-main.geosolutionsgroup.com/geoserver/web/<http://gs-main.geosolutionsgroup.com/geoserver/web/>", the proxy handles SSL and forwards the request as "http://<internal-gs-host>:8080/geoserver/web/<http://%3cinternal-gs-host%3e:8080/geoserver/web/>" and when doing a redirect the servlet container returns a HTTP 302 with a Location header stating "http://gs-main.geosolutionsgroup.com/geoserver/myChosenPath<http://gs-main.geosolutionsgroup.com/geoserver/myChosenPath>". Whoops!

So far everything worked anyways, because most sites have transitioned in recent years from HTTP to HTTPS and have a built-in configuration redirecting any HTTP request to HTTPS.
So it works by doing this:

  1.  GeoServer sends a redirect with Location header set to http://gs-main.geosolutionsgroup.com/geoserver/myChosenPath<http://gs-main.geosolutionsgroup.com/geoserver/myChosenPath>
  2.  The browser receives exactly that, and opens that new URL
  3.  The proxy in turns performs another redirect, this time to https://gs-main.geosolutionsgroup.com/geoserver/myChosenPath<http://gs-main.geosolutionsgroup.com/geoserver/myChosenPath>
  4.  The browser follows the new path and we're back in business
This happens on a set of very common actions in the GeoServer UI: login, logout, switch tab in the tabbed layer pages, click save in a number of pages where save is implemented as an Ajax button.

Introduce CSP, and the browser gets instructed not to reach out to pages outside of the origin server and protocol, and our little set of actions above stops at point 2., with errors only visible if you open the developer tools.

How to get out of it? I found and considered a few approaches.

-------------------------------------------------------------------------------------

First one: have GeoServer redirect to a full URL every time. That's allowed by the servlet API and we could build the full redirect URL by using the proxy base URL configuration. Redirects are done also in code outside of GeoServer, but this could be performed in a servlet wrapper.
However, I know for a fact it's going to break secure deploys that don't expose the GUI on the web... the typical situation there is that they access GeoServer directly within the DMZ, on the actual GeoServer IP, and the GUI needs to keep on working in that case.
We'd need some way to tell apart the local direct access from the "through proxy" access.
Which would mean, fiddling with the proxy configuration anyways. Meh!

Second one: tell the web container which protocol to use. The non standard, yet common, "X-Forwarded-Proto" header can be set to "https" as a way to tell the container which protocol it should use for redirects. However, containers will, out of the box, ignore it, because the header is not guarnteed to be there and it may be manipulated by clients to mount some sort of attack.
Futhermore, each container has a different way to configure using the header. For example, in Tomcat it would be declaring a Valve in server.xml:

<Valve className="org.apache.catalina.valves.RemoteIpValve"
       protocolHeader="X-Forwarded-Proto"
       remoteIpHeader="X-Forwarded-For"
       internalProxies=".*" />

But in Jetty, it would be something completely different in start.ini:

--module=forwarded

(mind, untested) and so on for each different servlet container.

Third one: tell the proxy to switch the protocol

The proxy can be configured to switch the proxy in redirect calls. Again, we're facing a case by case scenario.

For nginx (the case that I've actually tried, and can confirm it works):

proxy_redirect http://$host/ https://$host/;

For apache (mind, untested):

Header edit Location ^http://(.*)$ https://$1

and so on, a different way to do this in each proxy software.

-------------------------------------------------------------------------------------

Which one to choose? I've made a few questions around and asked people about this, as well as a few AIs, the summary is:

  *   SSL termination is normally in the hands of system admins, which may or may not dealing with the GeoServer setup
  *   Those same people are familiar with their proxy of choice, but very often, only lightly familiar with Tomcat configuration. Asking around about the Valve, I could not find anyone that knew what it was, while the nginx setting was known, although not normally used
  *   Asking AIs confirmed that web container setup is well known only in Java heavy shops, but a number of GeoServer deploys are in environments where GS is the only Java app around.
So I'd suggest to go an document how to configure proxies. I can offer an example of Nginx.
Can anyone else test the Apache approach? And then we can ask users to contribute approaches for other proxies, once the admins know what to do, they should be able to figure out the specific setting quickly.


Regards,

Andrea Aime



==

GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax:     +39 0584 1660272

mob:   +39  339 8844549


https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

-------------------------------------------------------

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati "GDPR"), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 "GDPR" - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail

________________________________

CONFIDENTIALITY NOTICE AND DISCLAIMER
The information in this transmission may be confidential and/or protected by legal professional privilege, and is intended only for the person or persons to whom it is addressed. If you are not such a person, you are warned that any disclosure, copying or dissemination of the information is unauthorised. If you have received the transmission in error, please immediately contact this office by telephone, fax or email, to inform us of the error and to enable arrangements to be made for the destruction of the transmission, or its return at our cost. No liability is accepted for any unauthorised use of the information contained in this transmission.

[Geoserver-devel] CSP with a proxy, how to deal with it

[Andrea A. <and...@ge...>]

Hi all,
I've spent some time trying to figure out how to attack the issue of CSP +
Proxy with SSL termination, this mail contains my findings (warning, long
and technical).

First of all, what's going on?
GeoServer code, Spring security, and Wicket internals, all tend to use
HTTPServletReponse.redirect("${relativePath}"), where relativePath is often
"web".

>From Servlet API javadoc
<https://javaee.github.io/javaee-spec/javadocs/javax/servlet/http/HttpServletResponse.html#sendRedirect-java.lang.String->
(thanks
Steve) we learn the method should be implemented by the container by
turning the relative path into an absolute URL.
That is done by taking the HTTP Host header, which is part of the spec and
guaranteed to be there, the context path (e.g., "geoserver") and the
relative path provided as an argument.

The protocol is an issue: there is not true standard HTTP header indicating
the protocol (there are non-standard headers though, more on this later),
so the servlet container will use whatever protocol it received the request
onto.

Now, it's pretty common practice that SSL is handled by proxy in front of
GeoServer, with nginx and apache being common choices. So the request goes
to, say "*https*://gs-main.geosolutionsgroup.com/geoserver/web/", the proxy
handles SSL and forwards the request as
"*http*://<internal-gs-host>:8080/geoserver/web/"
and when doing a redirect the servlet container returns a HTTP 302 with a
Location header stating "*http*://
gs-main.geosolutionsgroup.com/geoserver/myChosenPath". Whoops!

So far everything worked anyways, because most sites have transitioned in
recent years from HTTP to HTTPS and have a built-in configuration
redirecting any HTTP request to HTTPS.
So it works by doing this:

   1. GeoServer sends a redirect with Location header set to *http*://
   gs-main.geosolutionsgroup.com/geoserver/myChosenPath
   2. The browser receives exactly that, and opens that new URL
   3. The proxy in turns performs another redirect, this time to *https*://
   gs-main.geosolutionsgroup.com/geoserver/myChosenPath
   4. The browser follows the new path and we're back in business

This happens on a set of very common actions in the GeoServer UI: login,
logout, switch tab in the tabbed layer pages, click save in a number of
pages where save is implemented as an Ajax button.

Introduce CSP, and the browser gets instructed not to reach out to pages
outside of the origin server and protocol, and our little set of actions
above stops at point 2., with errors only visible if you open the developer
tools.

How to get out of it? I found and considered a few approaches.

-------------------------------------------------------------------------------------

*First one: have GeoServer redirect to a full URL every time*. That's
allowed by the servlet API and we could build the full redirect URL by
using the proxy base URL configuration. Redirects are done also in code
outside of GeoServer, but this could be performed in a servlet wrapper.
However, I know for a fact it's going to break secure deploys that don't
expose the GUI on the web... the typical situation there is that they
access GeoServer directly within the DMZ, on the actual GeoServer IP, and
the GUI needs to keep on working in that case.
We'd need some way to tell apart the local direct access from the "through
proxy" access.
Which would mean, fiddling with the proxy configuration anyways. Meh!

*Second one: tell the web container which protocol to use*. The non
standard, yet common, "X-Forwarded-Proto" header can be set to "https" as a
way to tell the container which protocol it should use for redirects.
However, containers will, out of the box, ignore it, because the header is
not guarnteed to be there and it may be manipulated by clients to mount
some sort of attack.
Futhermore, each container has a different way to configure using the
header. For example, in Tomcat it would be declaring a Valve in server.xml:

<Valve className="org.apache.catalina.valves.RemoteIpValve"
       protocolHeader="X-Forwarded-Proto"
       remoteIpHeader="X-Forwarded-For"
       internalProxies=".*" />

But in Jetty, it would be something completely different in start.ini:

--module=forwarded

(mind, untested) and so on for each different servlet container.

*Third one: tell the proxy to switch the protocol*

The proxy can be configured to switch the proxy in redirect calls. Again,
we're facing a case by case scenario.

For nginx (the case that I've actually tried, and can confirm it works):

proxy_redirect http://$host/ https://$host/;

For apache (mind, untested):

Header edit Location ^http://(.*)$ https://$1

and so on, a different way to do this in each proxy software.

-------------------------------------------------------------------------------------

Which one to choose? I've made a few questions around and asked people
about this, as well as a few AIs, the summary is:

   - SSL termination is normally in the hands of system admins, which may
   or may not dealing with the GeoServer setup
   - Those same people are familiar with their proxy of choice, but very
   often, only lightly familiar with Tomcat configuration. Asking around about
   the Valve, I could not find anyone that knew what it was, while the nginx
   setting was known, although not normally used
   - Asking AIs confirmed that web container setup is well known only in
   Java heavy shops, but a number of GeoServer deploys are in environments
   where GS is the only Java app around.

So I'd suggest to go an document how to configure proxies. I can offer an
example of Nginx.
Can anyone else test the Apache approach? And then we can ask users to
contribute approaches for other proxies, once the admins know what to do,
they should be able to figure out the specific setting quickly.

Regards,

Andrea Aime


==


GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax:     +39 0584 1660272

mob:   +39  339 8844549

https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

-------------------------------------------------------

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
precisa che ogni circostanza inerente alla presente email (il suo
contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is
addressed and may contain information that is privileged, confidential or
otherwise protected from disclosure. We remind that - as provided by
European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
e-mail or the information herein by anyone other than the intended
recipient is prohibited. If you have received this email by mistake, please
notify us immediately by telephone or e-mail

[Geoserver-devel] GeoServer pt-BR Translation

[Fernando Q. <fsq...@gm...>]

Hi All,

How are you? I was chatting with the GeoNode-BR WhatsApp Group today, and
they were saying that they had translated GeoNode to pt-BR using AI.

So I asked if there was any way to do this for GeoServer, and they said
they had already done it, so I would like to know from you what is the best
way to include this translation in the official version of GeoServer,
because the version that is currently available with GeoServer has words in
English, Portuguese and Spanish, and I would like to fix that.

I look forward to your recommendations.

Best regards,

Fernando Quadro
http://www.fernandoquadro.com.br
https://www.linkedin.com/in/fernandoquadro/

Re: [Geoserver-devel] Community space Fall 2024 cleanup

[Andrea A. <and...@ge...>]

Here: https://discourse.osgeo.org/t/community-space-fall-2024-cleanup/111311

Regards,

Andrea Aime


==


GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax:     +39 0584 1660272

mob:   +39  339 8844549

https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

-------------------------------------------------------

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
precisa che ogni circostanza inerente alla presente email (il suo
contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is
addressed and may contain information that is privileged, confidential or
otherwise protected from disclosure. We remind that - as provided by
European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
e-mail or the information herein by anyone other than the intended
recipient is prohibited. If you have received this email by mistake, please
notify us immediately by telephone or e-mail


On Tue, Nov 19, 2024 at 7:21 AM Jody Garnett <jod...@gm...> wrote:

> +1 of the cleanup changes, although you may also wish to post this to the
> forum?
>
> I assume this is just about clean up and not yet cutting scope...
> - -
> Jody Garnett
>
>
> On Nov 16, 2024 at 3:26:59 AM, Andrea Aime <
> and...@ge...> wrote:
>
>> Hi all,
>> it's been a while since the last community space cleanup, I guess it's
>> time to shed off some dead leaves again.
>>
>> Here is a list of modules that are in the community section, which do not
>> seem to have any action, value, or chance of being resurrected anytime soon:
>>
>>
>>    - app-schema/webservice-test
>>    <https://github.com/geoserver/geoserver/tree/main/src/community/app-schema/webservice-test>:
>>    run only with custom profiles (oddly, both "webservice" and
>>    "app-schema
>>    <https://github.com/geoserver/geoserver/blob/main/src/community/pom.xml#L102>"
>>    do). It does not even start to build, depends on the gone
>>    gt-webservice-test module.
>>    - gwc-distributed
>>    <https://github.com/geoserver/geoserver/tree/main/src/community/gwc-distributed>:
>>    containing just a Spring context and some dependencies, enables the Hazelcast
>>    distributed in memory tile cache
>>    <https://docs.geoserver.org/latest/en/user/geowebcache/config.html#hazelcast-cache>.
>>    Anyone using it?
>>    - imagemap
>>    <https://github.com/geoserver/geoserver/tree/main/src/community/imagemap>,
>>    enables the HTML image map output format
>>    <https://docs.geoserver.org/latest/en/user/community/imagemap.html>.
>>    I guess nobody today uses HTML image maps in cartography, but if you do,
>>    please let me know.
>>    - jdbc-metrics
>>    <https://github.com/geoserver/geoserver/tree/main/src/community/jdbc-metrics> seems
>>    to collect statistics about queries in JDBCFeatureReader
>>    <https://github.com/geotools/geotools/blob/main/modules/library/jdbc/src/main/java/org/geotools/jdbc/JDBCFeatureReader.java#L269>.
>>    On one side, it seems like a useful tool to track time actually spent
>>    talking to the database, on the other, it has no documentation has has seen
>>    to action for the past 7 years. Anyone using it, or that would be
>>    interested in writing a bit of documentation for it?
>>    - monitor-hibernate
>>    <https://github.com/geoserver/geoserver/tree/main/src/community/monitor-hibernate> provides
>>    database storage for the monitoring subsystem. Unmaintained, based on the
>>    dead Google code genericdao framework, and afflicted by using primary keys
>>    in a log table (insertions become slower and slower), it probably deserves
>>    some final rest, a suitable replacement would be a rewrite, not a few small
>>    fixes.
>>    - pgraster
>>    <https://github.com/geoserver/geoserver/tree/main/src/community/pgraster> despite
>>    the name it's an easy to use UI on top of  the no longer existing
>>    gt-imagemosaicjdbc.  This one already has a removal PR.
>>    - saml
>>    <https://github.com/geoserver/geoserver/tree/main/src/community/saml> is
>>    gone already, but its assembly descriptor survived and should also be
>>    removed.
>>    - wps-sextante
>>    <https://github.com/geoserver/geoserver/commits/main/src/community/wps-sextante> is
>>    based on the Sextante java libraries... which I cannot find any more. The
>>    version it depends onto has been released around 2012
>>    <https://mvnrepository.com/artifact/es.unex.sextante/sextante/1.0>,
>>    the module received its last direct commit in 2015 (all others are mass
>>    refactors), has no documentation, Sextante for Java seems nowhere to be
>>    found...
>>    - xslt
>>    <https://github.com/geoserver/geoserver/tree/main/src/community/xslt> is
>>    a WFS output format generator based on XSLT that was demoted to community
>>    in May 2023. Looks like nobody complained, I'd complete the job.
>>
>> Regarding extensions, the following look like good candidates for
>> demotion to community:
>>
>>    - h2
>>    <https://github.com/geoserver/geoserver/tree/main/src/extension/h2>
>>    store, based on the old and unmaintained H2 v1.x. While we cannot get rid
>>    of it completely, as some modules keep on depending on it (e.g. the NetCDF
>>    store family), I'd make its availability as a vector store harder to get.
>>
>> Feedback welcomed!
>>
>> Regards,
>>
>> Andrea Aime
>>
>>
>> ==
>>
>>
>> GeoServer Professional Services from the experts!
>>
>> Visit http://bit.ly/gs-services-us for more information.
>>
>> ==
>>
>> Ing. Andrea Aime
>> @geowolf
>> Technical Lead
>>
>> GeoSolutions Group
>> phone: +39 0584 962313
>>
>> fax:     +39 0584 1660272
>>
>> mob:   +39  339 8844549
>>
>> https://www.geosolutionsgroup.com/
>>
>> http://twitter.com/geosolutions_it
>>
>> -------------------------------------------------------
>>
>> Con riferimento alla normativa sul trattamento dei dati personali (Reg.
>> UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
>> precisa che ogni circostanza inerente alla presente email (il suo
>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>>
>> This email is intended only for the person or entity to which it is
>> addressed and may contain information that is privileged, confidential or
>> otherwise protected from disclosure. We remind that - as provided by
>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
>> e-mail or the information herein by anyone other than the intended
>> recipient is prohibited. If you have received this email by mistake, please
>> notify us immediately by telephone or e-mail
>> _______________________________________________
>> Geoserver-devel mailing list
>> Geo...@li...
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>

Re: [Geoserver-devel] Community space Fall 2024 cleanup

[Jody G. <jod...@gm...>]

 +1 of the cleanup changes, although you may also wish to post this to the
forum?

I assume this is just about clean up and not yet cutting scope...
- -
Jody Garnett


On Nov 16, 2024 at 3:26:59 AM, Andrea Aime <
and...@ge...> wrote:

> Hi all,
> it's been a while since the last community space cleanup, I guess it's
> time to shed off some dead leaves again.
>
> Here is a list of modules that are in the community section, which do not
> seem to have any action, value, or chance of being resurrected anytime soon:
>
>
>    - app-schema/webservice-test
>    <https://github.com/geoserver/geoserver/tree/main/src/community/app-schema/webservice-test>:
>    run only with custom profiles (oddly, both "webservice" and "app-schema
>    <https://github.com/geoserver/geoserver/blob/main/src/community/pom.xml#L102>"
>    do). It does not even start to build, depends on the gone
>    gt-webservice-test module.
>    - gwc-distributed
>    <https://github.com/geoserver/geoserver/tree/main/src/community/gwc-distributed>:
>    containing just a Spring context and some dependencies, enables the Hazelcast
>    distributed in memory tile cache
>    <https://docs.geoserver.org/latest/en/user/geowebcache/config.html#hazelcast-cache>.
>    Anyone using it?
>    - imagemap
>    <https://github.com/geoserver/geoserver/tree/main/src/community/imagemap>,
>    enables the HTML image map output format
>    <https://docs.geoserver.org/latest/en/user/community/imagemap.html>. I
>    guess nobody today uses HTML image maps in cartography, but if you do,
>    please let me know.
>    - jdbc-metrics
>    <https://github.com/geoserver/geoserver/tree/main/src/community/jdbc-metrics> seems
>    to collect statistics about queries in JDBCFeatureReader
>    <https://github.com/geotools/geotools/blob/main/modules/library/jdbc/src/main/java/org/geotools/jdbc/JDBCFeatureReader.java#L269>.
>    On one side, it seems like a useful tool to track time actually spent
>    talking to the database, on the other, it has no documentation has has seen
>    to action for the past 7 years. Anyone using it, or that would be
>    interested in writing a bit of documentation for it?
>    - monitor-hibernate
>    <https://github.com/geoserver/geoserver/tree/main/src/community/monitor-hibernate> provides
>    database storage for the monitoring subsystem. Unmaintained, based on the
>    dead Google code genericdao framework, and afflicted by using primary keys
>    in a log table (insertions become slower and slower), it probably deserves
>    some final rest, a suitable replacement would be a rewrite, not a few small
>    fixes.
>    - pgraster
>    <https://github.com/geoserver/geoserver/tree/main/src/community/pgraster> despite
>    the name it's an easy to use UI on top of  the no longer existing
>    gt-imagemosaicjdbc.  This one already has a removal PR.
>    - saml
>    <https://github.com/geoserver/geoserver/tree/main/src/community/saml> is
>    gone already, but its assembly descriptor survived and should also be
>    removed.
>    - wps-sextante
>    <https://github.com/geoserver/geoserver/commits/main/src/community/wps-sextante> is
>    based on the Sextante java libraries... which I cannot find any more. The
>    version it depends onto has been released around 2012
>    <https://mvnrepository.com/artifact/es.unex.sextante/sextante/1.0>,
>    the module received its last direct commit in 2015 (all others are mass
>    refactors), has no documentation, Sextante for Java seems nowhere to be
>    found...
>    - xslt
>    <https://github.com/geoserver/geoserver/tree/main/src/community/xslt> is
>    a WFS output format generator based on XSLT that was demoted to community
>    in May 2023. Looks like nobody complained, I'd complete the job.
>
> Regarding extensions, the following look like good candidates for demotion
> to community:
>
>    - h2
>    <https://github.com/geoserver/geoserver/tree/main/src/extension/h2>
>    store, based on the old and unmaintained H2 v1.x. While we cannot get rid
>    of it completely, as some modules keep on depending on it (e.g. the NetCDF
>    store family), I'd make its availability as a vector store harder to get.
>
> Feedback welcomed!
>
> Regards,
>
> Andrea Aime
>
>
> ==
>
>
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
>
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax:     +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> _______________________________________________
> Geoserver-devel mailing list
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>

[Geoserver-devel] GeoTools 32.1, GeoServer 2.26.1, GeoWebCache 1.26.1 release starting tomorrow

[Peter S. <gs...@sm...>]

Good morning from South Africa

I will be starting the above releases tomorrow morning.  If you have any
urgent fixes that you would like in these versions, please submit PRs, or
let me know to wait for them.

Thank you

Peter

GeoServer PSC
AWS Solutions Architect
https://github.com/petersmythe

[Geoserver-devel] Community space Fall 2024 cleanup

[Andrea A. <and...@ge...>]

Hi all,
it's been a while since the last community space cleanup, I guess it's time
to shed off some dead leaves again.

Here is a list of modules that are in the community section, which do not
seem to have any action, value, or chance of being resurrected anytime soon:


   - app-schema/webservice-test
   <https://github.com/geoserver/geoserver/tree/main/src/community/app-schema/webservice-test>:
   run only with custom profiles (oddly, both "webservice" and "app-schema
   <https://github.com/geoserver/geoserver/blob/main/src/community/pom.xml#L102>"
   do). It does not even start to build, depends on the gone
   gt-webservice-test module.
   - gwc-distributed
   <https://github.com/geoserver/geoserver/tree/main/src/community/gwc-distributed>:
   containing just a Spring context and some dependencies, enables the
Hazelcast
   distributed in memory tile cache
   <https://docs.geoserver.org/latest/en/user/geowebcache/config.html#hazelcast-cache>.
   Anyone using it?
   - imagemap
   <https://github.com/geoserver/geoserver/tree/main/src/community/imagemap>,
   enables the HTML image map output format
   <https://docs.geoserver.org/latest/en/user/community/imagemap.html>. I
   guess nobody today uses HTML image maps in cartography, but if you do,
   please let me know.
   - jdbc-metrics
   <https://github.com/geoserver/geoserver/tree/main/src/community/jdbc-metrics>
seems
   to collect statistics about queries in JDBCFeatureReader
   <https://github.com/geotools/geotools/blob/main/modules/library/jdbc/src/main/java/org/geotools/jdbc/JDBCFeatureReader.java#L269>.
   On one side, it seems like a useful tool to track time actually spent
   talking to the database, on the other, it has no documentation has has seen
   to action for the past 7 years. Anyone using it, or that would be
   interested in writing a bit of documentation for it?
   - monitor-hibernate
   <https://github.com/geoserver/geoserver/tree/main/src/community/monitor-hibernate>
provides
   database storage for the monitoring subsystem. Unmaintained, based on the
   dead Google code genericdao framework, and afflicted by using primary keys
   in a log table (insertions become slower and slower), it probably deserves
   some final rest, a suitable replacement would be a rewrite, not a few small
   fixes.
   - pgraster
   <https://github.com/geoserver/geoserver/tree/main/src/community/pgraster>
despite
   the name it's an easy to use UI on top of  the no longer existing
   gt-imagemosaicjdbc.  This one already has a removal PR.
   - saml
   <https://github.com/geoserver/geoserver/tree/main/src/community/saml> is
   gone already, but its assembly descriptor survived and should also be
   removed.
   - wps-sextante
   <https://github.com/geoserver/geoserver/commits/main/src/community/wps-sextante>
is
   based on the Sextante java libraries... which I cannot find any more. The
   version it depends onto has been released around 2012
   <https://mvnrepository.com/artifact/es.unex.sextante/sextante/1.0>, the
   module received its last direct commit in 2015 (all others are mass
   refactors), has no documentation, Sextante for Java seems nowhere to be
   found...
   - xslt
   <https://github.com/geoserver/geoserver/tree/main/src/community/xslt> is
   a WFS output format generator based on XSLT that was demoted to community
   in May 2023. Looks like nobody complained, I'd complete the job.

Regarding extensions, the following look like good candidates for demotion
to community:

   - h2 <https://github.com/geoserver/geoserver/tree/main/src/extension/h2>
   store, based on the old and unmaintained H2 v1.x. While we cannot get rid
   of it completely, as some modules keep on depending on it (e.g. the NetCDF
   store family), I'd make its availability as a vector store harder to get.

Feedback welcomed!

Regards,

Andrea Aime


==


GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax:     +39 0584 1660272

mob:   +39  339 8844549

https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

-------------------------------------------------------

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
precisa che ogni circostanza inerente alla presente email (il suo
contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is
addressed and may contain information that is privileged, confidential or
otherwise protected from disclosure. We remind that - as provided by
European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
e-mail or the information herein by anyone other than the intended
recipient is prohibited. If you have received this email by mistake, please
notify us immediately by telephone or e-mail

[Geoserver-devel] Upgradation of Geoserver

[Muhammad A. <asi...@gm...>]

Dear Team,

I am reaching out to request guidance on upgrading two production GeoServer
instances, currently running versions 2.17.2 and 2.18.0, to the latest
version, 2.26.0. My goal is to ensure a secure and stable upgrade process
for both instances, particularly given the differences in their current
versions and potential patching gaps.

*Concerns and Considerations for the Upgrade:*

   1.

   *Patch Status of 2.17.2 and 2.18.0*:
   - Could you confirm whether GeoServer 2.17.2 is considered "unpatched"
      compared to later releases and clarify if any critical patches were
      introduced in 2.18.0 that are absent in 2.17.2? An overview of the key
      security or stability fixes included in 2.18.0 and later
versions would be
      very helpful for planning this upgrade.
   2.

   *Compatibility and Configuration Considerations in 2.26.0*:
   - Are there any known compatibility changes in version 2.26.0 that could
      impact configurations created in 2.17.2 or 2.18.0? In particular, I am
      interested in ensuring that the existing data directory structure,
      workspace setups, styles, and datastore connections will remain
compatible
      after the upgrade.
      - Could you advise on any verification steps or compatibility checks
      to confirm that our current settings will work seamlessly with version
      2.26.0?
   3.

   *Upgrade Path and Best Practices*:
   - Given the two production instances on different versions, would you
      recommend an incremental upgrade path (e.g., 2.18.0 to 2.20.x, then to
      2.26.0) or a direct upgrade to 2.26.0 for both?
      - Are there specific staging or testing practices you would suggest
      to minimize downtime and ensure a stable production environment
during and
      after the upgrade?
   4.

   *Security and Performance Enhancements in 2.26.0*:
   - Could you highlight any significant security improvements, performance
      optimizations, or critical bug fixes in 2.26.0 compared to 2.17.2 and
      2.18.0? Knowing these would help emphasize the upgrade's value to our
      stakeholders.
   5.

   *Data Directory Separation*:
   - Both GeoServer instances currently operate with separated data_dir
      configurations from the main application directory. Are there
any specific
      considerations for maintaining data integrity and compatibility with this
      structure in 2.26.0?

I would greatly appreciate any additional insights, documentation, or
suggestions from your team to help facilitate a smooth upgrade process for
these production instances.

Thank you for your assistance and for your ongoing work on GeoServer.

*Regards,*

*Muhammad Asif  **|*GIS Developer*|*

Mob: +92 300 812 91 65

[Geoserver-devel] Final message to geoserver-devel mailing list

[Jody G. <jod...@gm...>]

List now closed, join us on GeoServer Developer forum:
https://discourse.osgeo.org/invites/7DX66egwux
--
GeoServer Project Steering Committee

Re: [Geoserver-devel] Serious unit testing issue: all modules with GUI run exactly 0 tests

[David B. <dav...@ge...>]

Hi, Andrea,

Since there's only 4 pages that are having issues (3% test fails), I think
it would be better to try to fix the test case than back-out the changes.

I'll see if I can come to the GS meeting this morning.

Dave

On Tue, Oct 8, 2024 at 6:02 AM Andrea Aime <
and...@ge...> wrote:

> Hì all,
> Daniele just reported me some mysterious issues with the MapML module: the
> build was running no tests at all, just passing without executing a single
> one.
>
> We looked into it, and all modules where the new junit-jupiter (JUnit 5)
> dependency has been added, fail to run the JUnit 4 tests. The dependency
> has been added as part of the Wicket 9 upgrade merge, as the new Wicket
> testing framework needs the JUnit 5 classes in the classpath.
>
> The issue is that surefire picks the JUnit runner based on what's in the
> classpath, if it finds JUnit5, it will only run JUnit5 tests.
>
> Now... I could understand if this affected a few modules that are mixing
> in wicket dependencies, but even web-core builds with the following:
>
> [INFO] Results:
> [INFO]
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
>
> One way to have the Junit 4 tests to run, is to have the junit-vintage
> engine installed, which is still part of JUnit5, but able to run JUnit4
> tests. I've tried on web-cor, and the result looks grim... once the tests
> start running, there's quite a bit of failures:
>
> [ERROR] Failures:
> [ERROR]   LayerGroupEditPageTest.testLayerGroupLinkWithWorkspace:299 path:
> 'publishedinfo:tabs:panel:layers:popup:content:listContainer:items' does
> not exist for page: LayerGroupEditPage
> [ERROR]   LayerGroupEditPageTest.testLayerGroupStyle:722 path:
> 'publishedinfo:tabs:panel:layerGroupStyles:listContainer:styleList:0:layerGroupStylePanel:layerGroupEntryPanel:popup:content:listContainer:items:1:itemProperties:0:component:link'
> does not exist for page: LayerGroupEditPage
> [ERROR]   LayerGroupEditPageTest.testLayerGroupStyle2:775 path:
> 'publishedinfo:tabs:panel:layerGroupStyles:listContainer:styleList:0:layerGroupStylePanel:layerGroupEntryPanel:popup:content:listContainer:items:3:itemProperties:0:component:link'
> does not exist for page: LayerGroupEditPage
> [ERROR]   LayerGroupEditPageTest.testLayerGroupStyleSelection:862 path:
> 'publishedinfo:tabs:panel:layerGroupStyles:listContainer:styleList:0:layerGroupStylePanel:layerGroupEntryPanel:popup:content:listContainer:items:2:itemProperties:0:component:link'
> does not exist for page: LayerGroupEditPage
> [ERROR]   LayerGroupEditPageTest.testLayerLink:212 path:
> 'publishedinfo:tabs:panel:layers:popup:content:listContainer:items' does
> not exist for page: LayerGroupEditPage
> [ERROR]   LayerGroupEditPageTest.testLayerLinkWithWorkspace:265 path:
> 'publishedinfo:tabs:panel:layers:popup:content:listContainer:items' does
> not exist for page: LayerGroupEditPage
> [ERROR]   LayerGroupEditPageTest.testStyleGroupLink:238 path:
> 'publishedinfo:tabs:panel:layers:popup:content:listContainer:items' does
> not exist for page: LayerGroupEditPage
> [ERROR]   ResourceConfigurationPageTest.testConsistentUpdateWMTSBbox:834
> path:
> 'publishedinfo:tabs:panel:theList:0:content:referencingForm:nativeSRS:popup:content:table:listContainer:items:1:itemProperties:0:component:link'
> does not exist for page: ResourceConfigurationPage
> [ERROR]   ResourceConfigurationPageTest.testWFSDataStoreResource:467 path:
> 'publishedinfo:tabs:panel:theList:0:content:referencingForm:nativeSRS:popup:content:table:listContainer:items:1:itemProperties:0:component:link'
> does not exist for page: ResourceConfigurationPage
> [ERROR]   ResourceConfigurationPageTest.testWMTSOtherCRS:584 path:
> 'publishedinfo:tabs:panel:theList:0:content:referencingForm:nativeSRS:popup:content:table:listContainer:items:1:itemProperties:0:component:link'
> does not exist for page: ResourceConfigurationPage
> [ERROR]   ResourceConfigurationPageTest.testWMTSOtherCRSUrnFormat:622
> path:
> 'publishedinfo:tabs:panel:theList:0:content:referencingForm:nativeSRS:popup:content:table:listContainer:items'
> does not exist for page: ResourceConfigurationPage
> [ERROR]   CRSPanelTest.testPlanetaryList:245 Unable to set value. Couldn't
> find component with name: crs:popup:content:table:filterForm:filter ==>
> expected: not <null>
> [ERROR]   CRSPanelTest.testPlanetaryPopupWindow:227 path:
> 'form:crs:popup:content:wkt' does not exist for page: CRSPanelTestPage
> [ERROR]   CRSPanelTest.testPopupWindow:69 path:
> 'form:crs:popup:content:wkt' does not exist for page: CRSPanelTestPage
> [ERROR] Errors:
> [ERROR]   GeoServerAboutPageTest.testHideSensitiveInfo:40 » WicketRuntime
> The component(...
> [ERROR]   GeoServerAboutPageTest.testLoginFormAction:21 » WicketRuntime
> The component(s)...
> [INFO]
> [ERROR] Tests run: 405, Failures: 14, Errors: 2, Skipped: 10
> [INFO]
>
> This is just web-core... how many more are broken?
>
> I think the Wicket 9 merge should be reverted until it actually builds.
> Opinions?
>
> Regards,
>
> Andrea Aime
>
>
> ==
>
>
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
>
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax:     +39 0584 1660272
>
> mob:   +39  339 8844549
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
> _______________________________________________
> Geoserver-devel mailing list
> Geo...@li...
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>

[Geoserver-devel] Serious unit testing issue: all modules with GUI run exactly 0 tests

[Andrea A. <and...@ge...>]

Hì all,
Daniele just reported me some mysterious issues with the MapML module: the
build was running no tests at all, just passing without executing a single
one.

We looked into it, and all modules where the new junit-jupiter (JUnit 5)
dependency has been added, fail to run the JUnit 4 tests. The dependency
has been added as part of the Wicket 9 upgrade merge, as the new Wicket
testing framework needs the JUnit 5 classes in the classpath.

The issue is that surefire picks the JUnit runner based on what's in the
classpath, if it finds JUnit5, it will only run JUnit5 tests.

Now... I could understand if this affected a few modules that are mixing in
wicket dependencies, but even web-core builds with the following:

[INFO] Results:
[INFO]
[INFO] Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

One way to have the Junit 4 tests to run, is to have the junit-vintage
engine installed, which is still part of JUnit5, but able to run JUnit4
tests. I've tried on web-cor, and the result looks grim... once the tests
start running, there's quite a bit of failures:

[ERROR] Failures:
[ERROR]   LayerGroupEditPageTest.testLayerGroupLinkWithWorkspace:299 path:
'publishedinfo:tabs:panel:layers:popup:content:listContainer:items' does
not exist for page: LayerGroupEditPage
[ERROR]   LayerGroupEditPageTest.testLayerGroupStyle:722 path:
'publishedinfo:tabs:panel:layerGroupStyles:listContainer:styleList:0:layerGroupStylePanel:layerGroupEntryPanel:popup:content:listContainer:items:1:itemProperties:0:component:link'
does not exist for page: LayerGroupEditPage
[ERROR]   LayerGroupEditPageTest.testLayerGroupStyle2:775 path:
'publishedinfo:tabs:panel:layerGroupStyles:listContainer:styleList:0:layerGroupStylePanel:layerGroupEntryPanel:popup:content:listContainer:items:3:itemProperties:0:component:link'
does not exist for page: LayerGroupEditPage
[ERROR]   LayerGroupEditPageTest.testLayerGroupStyleSelection:862 path:
'publishedinfo:tabs:panel:layerGroupStyles:listContainer:styleList:0:layerGroupStylePanel:layerGroupEntryPanel:popup:content:listContainer:items:2:itemProperties:0:component:link'
does not exist for page: LayerGroupEditPage
[ERROR]   LayerGroupEditPageTest.testLayerLink:212 path:
'publishedinfo:tabs:panel:layers:popup:content:listContainer:items' does
not exist for page: LayerGroupEditPage
[ERROR]   LayerGroupEditPageTest.testLayerLinkWithWorkspace:265 path:
'publishedinfo:tabs:panel:layers:popup:content:listContainer:items' does
not exist for page: LayerGroupEditPage
[ERROR]   LayerGroupEditPageTest.testStyleGroupLink:238 path:
'publishedinfo:tabs:panel:layers:popup:content:listContainer:items' does
not exist for page: LayerGroupEditPage
[ERROR]   ResourceConfigurationPageTest.testConsistentUpdateWMTSBbox:834
path:
'publishedinfo:tabs:panel:theList:0:content:referencingForm:nativeSRS:popup:content:table:listContainer:items:1:itemProperties:0:component:link'
does not exist for page: ResourceConfigurationPage
[ERROR]   ResourceConfigurationPageTest.testWFSDataStoreResource:467 path:
'publishedinfo:tabs:panel:theList:0:content:referencingForm:nativeSRS:popup:content:table:listContainer:items:1:itemProperties:0:component:link'
does not exist for page: ResourceConfigurationPage
[ERROR]   ResourceConfigurationPageTest.testWMTSOtherCRS:584 path:
'publishedinfo:tabs:panel:theList:0:content:referencingForm:nativeSRS:popup:content:table:listContainer:items:1:itemProperties:0:component:link'
does not exist for page: ResourceConfigurationPage
[ERROR]   ResourceConfigurationPageTest.testWMTSOtherCRSUrnFormat:622 path:
'publishedinfo:tabs:panel:theList:0:content:referencingForm:nativeSRS:popup:content:table:listContainer:items'
does not exist for page: ResourceConfigurationPage
[ERROR]   CRSPanelTest.testPlanetaryList:245 Unable to set value. Couldn't
find component with name: crs:popup:content:table:filterForm:filter ==>
expected: not <null>
[ERROR]   CRSPanelTest.testPlanetaryPopupWindow:227 path:
'form:crs:popup:content:wkt' does not exist for page: CRSPanelTestPage
[ERROR]   CRSPanelTest.testPopupWindow:69 path:
'form:crs:popup:content:wkt' does not exist for page: CRSPanelTestPage
[ERROR] Errors:
[ERROR]   GeoServerAboutPageTest.testHideSensitiveInfo:40 » WicketRuntime
The component(...
[ERROR]   GeoServerAboutPageTest.testLoginFormAction:21 » WicketRuntime The
component(s)...
[INFO]
[ERROR] Tests run: 405, Failures: 14, Errors: 2, Skipped: 10
[INFO]

This is just web-core... how many more are broken?

I think the Wicket 9 merge should be reverted until it actually builds.
Opinions?

Regards,

Andrea Aime


==


GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax:     +39 0584 1660272

mob:   +39  339 8844549

https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

-------------------------------------------------------

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
precisa che ogni circostanza inerente alla presente email (il suo
contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is
addressed and may contain information that is privileged, confidential or
otherwise protected from disclosure. We remind that - as provided by
European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
e-mail or the information herein by anyone other than the intended
recipient is prohibited. If you have received this email by mistake, please
notify us immediately by telephone or e-mail

Re: [Geoserver-devel] Status Update OAuth2 migration

[Jody G. <jod...@gm...>]

Hi Andreas,

Catching up with developer activities - many weeks later. I am writing a
blog post for Q4 and wanted to mention the great work you are doing.

I note one topic did not get feedback:

- The Java package namespace of the existing modules is
> "org.geoserver.security.oauth2." Should we keep this? Pro: The name fits
> and renaming would require effort. Con: If users install both the previous
> and the migrated modules together — which certainly won’t work — the
> conflict may not be immediately apparent. My suggestion is to keep the
> package name.
>

I like the idea of keeping the package name, but it may make it complicated
for those working in an IDE with both modules loaded (say during a
refactor)?