Re: [Geoserver-users] Geometry type mismatch

2024-04-22 Thread Rahkonen Jukka 
Hi,

I made a test with Geoserver 2.25.0 and I can confirm that there is a mismatch 
between DescribeFeatureType and GetFeature for ne:countries with WFS 1.1.0.
I tried to test also topp:states but it seems that there is something else 
broken with that. GetFeature with WFS 1.1.0 and WFS 2.0 returns this error:


We have had issues trying to flip axis of 
GEOGCS["GCS_WGS_1984", DATUM["WGS_1984", SPHEROID["WGS_1984", 6378137.0, 
298.257223563]], PRIMEM["Greenwich", 0.0], UNIT["degree", 
0.017453292519943295], AXIS["Longitude", EAST], AXIS["Latitude", NORTH]] No 
authority was defined for code "GCS_WGS_1984". Did you forget 
"AUTHORITY:NUMBER"?

I was testing with a new Geoserver binzip installation on Windows, JVM Eclipse 
Adoptium: 11.0.22.

-Jukka Rahkonen-



Lähettäjä: Ian Turton 
Lähetetty: maanantai 22. huhtikuuta 2024 19.00
Vastaanottaja: Calliess Daniel Ing. 
Kopio: geoserver-users 
Aihe: Re: [Geoserver-users] Geometry type mismatch



On Mon, 22 Apr 2024 at 16:29, Calliess Daniel Ing. 
mailto:daniel.calli...@stadt-salzburg.at>> 
wrote:
Hi,

after upgrading GeoServer from 2.24.0 to 2.24.1 one of my users

Please look into this and correct the error.

Please remember that GeoServer is maintained by volunteers - if your users have 
a problem then they are (presumably) paying you to take care of it. If you are 
not up to fixing the problem yourself please contact one of the commercial 
support teams that will look into it for you.

Ian
--
Ian Turton
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Geometry type mismatch

2024-04-22 Thread Ian Turton 
On Mon, 22 Apr 2024 at 16:29, Calliess Daniel Ing. <
daniel.calli...@stadt-salzburg.at> wrote:

> Hi,
>
>
>
> after upgrading GeoServer from 2.24.0 to 2.24.1 one of *my users*
>
>
>
> *Please look into this and correct the error.*
>

Please remember that GeoServer is maintained by volunteers - if your users
have a problem then they are (presumably) paying you to take care of it. If
you are not up to fixing the problem yourself please contact one of
the commercial
support teams  that will look into it for
you.

Ian
-- 
Ian Turton
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

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

2024-04-22 Thread Calliess Daniel Ing . 
Hello Jean-Christophe,

when users upload XML documents to your server those files can contain links to 
other documents (f.e. for namespace or schema definitions). An attacker could 
send a document containing links to files on the server's disk and somehow 
cause the server to leak this information I think. Or include links to 
ressources on the internet that lead GeoServer to misbehave. More specific 
information might come from the GeoServer developers. See also 
https://docs.geoserver.org/latest/en/user/configuration/globalsettings.html#config-globalsettings-external-entities
 in the documenation.

So I'm trying to avoid weakening the External Entity settings if possible. And 
also would suggest you use the "-DENTITY_RESOLUTION_ALLOWLIST=*" parameter (see 
https://docs.geoserver.org/latest/en/user/production/config.html#production-config-external-entities)
 for the moment because it only allows access to online ressources, not to 
local files on the server.

Regards
Daniel


From: Jean-Christophe Bastin 
Sent: Montag, 22. April 2024 16:41
To: Calliess Daniel Ing. ; 'geoserver-users' 

Subject: RE: WMS broken after GeoServer Update (SAXException)

Hello Daniel,

I found a solution. I don't know if this is the same behavior than your 
parameter DENTITY_RESOLUTION_ALLOWLIST=*.
In Configuration, Global, you have "Unlimited resolution of XML external 
entities (security risk)" (this is translated from french, sorry if it's not 
exactly the same words).
After checked and applied changes, the error is gone when consulting layers.
BUT, I see the "security risk" with this parameter, and I don't know what is it 
exactly.

If someone can explain what is it talking about, I'll appreciate it :)

Many thanks.

Jean-Christophe

De : Jean-Christophe Bastin
Envoyé : lundi 22 avril 2024 16:13
À : Calliess Daniel Ing. 
mailto:daniel.calli...@stadt-salzburg.at>>; 
'geoserver-users' 
mailto:geoserver-users@lists.sourceforge.net>>
Objet : RE: WMS broken after GeoServer Update (SAXException)

Hello,

I was about to write an equivalent message to the community for the same error.
In my case, I'm updating from GeoServer 2.10.0 to 2.25.0. I had many issues 
that I was able to manage by myself. But the last issue (I hope) I see now is 
for any layer I want to preview, or access to show, I get also a service 
exception 
"java.lang.reflect.UndeclaredThrowableExceptionorg.xml.sax.SAXException: Entity 
resolution disallowed for null".

I'm really interested to have also some support on this point.

Many thanks.

Jean-Christophe

De : Calliess Daniel Ing. 
mailto:daniel.calli...@stadt-salzburg.at>>
Envoyé : lundi 22 avril 2024 15:00
À : 'geoserver-users' 
mailto:geoserver-users@lists.sourceforge.net>>
Objet : [Geoserver-users] WMS broken after GeoServer Update (SAXException)

Hi,

I updated my GeoServer (Tomcat 9/Windows Server) from 2.24.2 to 2.25.0 and now 
I can't preview WMS layers. The error message is: 
"java.lang.reflect.UndeclaredThrowableExceptionorg.xml.sax.SAXException: Entity 
resolution disallowed for null". The same message is shown when I try to 
validate an SLD stylesheet. I copied the full stack trace to a file and 
attached it to this message. I also reverted back to the data dir included in 
the 2.25.0 release and can reproduce the error f.e. with the 'point' style.

I now found out that when I'm starting GeoServer with the 
-DENTITY_RESOLUTION_ALLOWLIST=* parameter, the error is gone. Although this 
parameter shouldn't be necessary because the styles are only containing 
references to www.opengis.net and 
www.w3.org which are in the default list of allowed domains 
for entity expansion according to the 
documentation.

The geoserver log shows a lot of "WARN   [geotools.xsd] - Sax parser property 
'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' not 
recognized.  Xerces version is incompatible." messages. Might there be a 
connection to the above issue?

Am I doing something wrong?

Thank you and best regards
Daniel
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

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

2024-04-22 Thread Jean-Christophe Bastin 
Hello,

I was about to write an equivalent message to the community for the same error.
In my case, I'm updating from GeoServer 2.10.0 to 2.25.0. I had many issues 
that I was able to manage by myself. But the last issue (I hope) I see now is 
for any layer I want to preview, or access to show, I get also a service 
exception 
"java.lang.reflect.UndeclaredThrowableExceptionorg.xml.sax.SAXException: Entity 
resolution disallowed for null".

I'm really interested to have also some support on this point.

Many thanks.

Jean-Christophe

De : Calliess Daniel Ing. 
Envoyé : lundi 22 avril 2024 15:00
À : 'geoserver-users' 
Objet : [Geoserver-users] WMS broken after GeoServer Update (SAXException)

Hi,

I updated my GeoServer (Tomcat 9/Windows Server) from 2.24.2 to 2.25.0 and now 
I can't preview WMS layers. The error message is: 
"java.lang.reflect.UndeclaredThrowableExceptionorg.xml.sax.SAXException: Entity 
resolution disallowed for null". The same message is shown when I try to 
validate an SLD stylesheet. I copied the full stack trace to a file and 
attached it to this message. I also reverted back to the data dir included in 
the 2.25.0 release and can reproduce the error f.e. with the 'point' style.

I now found out that when I'm starting GeoServer with the 
-DENTITY_RESOLUTION_ALLOWLIST=* parameter, the error is gone. Although this 
parameter shouldn't be necessary because the styles are only containing 
references to www.opengis.net and 
www.w3.org which are in the default list of allowed domains 
for entity expansion according to the 
documentation.

The geoserver log shows a lot of "WARN   [geotools.xsd] - Sax parser property 
'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' not 
recognized.  Xerces version is incompatible." messages. Might there be a 
connection to the above issue?

Am I doing something wrong?

Thank you and best regards
Daniel
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] Geometry type mismatch

2024-04-22 Thread Calliess Daniel Ing . 
Hi,

after upgrading GeoServer from 2.24.0 to 2.24.1 one of my users was unable to 
process data from the WFS service in the software FME. The problem comes from 
the fact that the feature type returned in the GetFeature request doesn't match 
the feature type declared in the DescribeFeatureType request when accessing the 
service using WFS 1.1.0. In this case FME doesn't detect the geometries.

This can be reproduced using the 'ne:countries' layer in a new GeoServer 
installation. This is what my tests showed:

GeoServer 2.24.0
WFS 1.0.0
   GetFeature = MultiPolygon
   DescribeFeatureType = MultiPolygonPropertyType
WFS 1.1.0
   GetFeature = MultiSurface
   DescribeFeatureType = MultiSurfacePropertyType
WFS 2.0.0
   GetFeature = MultiSurface
   DescribeFeatureType = MultiSurfacePropertyType

GeoServer 2.24.1
WFS 1.0.0
   GetFeature = MultiPolygon
   DescribeFeatureType = MultiPolygonPropertyType
WFS 1.1.0
   GetFeature = MultiSurface
   DescribeFeatureType = MultiPolygonPropertyType
WFS 2.0.0
   GetFeature = MultiSurface
   DescribeFeatureType = MultiSurfacePropertyType

Please look into this and correct the error.

Thank you and best regards
Daniel
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

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

2024-04-22 Thread Jean-Christophe Bastin 
Hello Daniel,

I found a solution. I don't know if this is the same behavior than your 
parameter DENTITY_RESOLUTION_ALLOWLIST=*.
In Configuration, Global, you have "Unlimited resolution of XML external 
entities (security risk)" (this is translated from french, sorry if it's not 
exactly the same words).
After checked and applied changes, the error is gone when consulting layers.
BUT, I see the "security risk" with this parameter, and I don't know what is it 
exactly.

If someone can explain what is it talking about, I'll appreciate it :)

Many thanks.

Jean-Christophe

De : Jean-Christophe Bastin
Envoyé : lundi 22 avril 2024 16:13
À : Calliess Daniel Ing. ; 'geoserver-users' 

Objet : RE: WMS broken after GeoServer Update (SAXException)

Hello,

I was about to write an equivalent message to the community for the same error.
In my case, I'm updating from GeoServer 2.10.0 to 2.25.0. I had many issues 
that I was able to manage by myself. But the last issue (I hope) I see now is 
for any layer I want to preview, or access to show, I get also a service 
exception 
"java.lang.reflect.UndeclaredThrowableExceptionorg.xml.sax.SAXException: Entity 
resolution disallowed for null".

I'm really interested to have also some support on this point.

Many thanks.

Jean-Christophe

De : Calliess Daniel Ing. 
mailto:daniel.calli...@stadt-salzburg.at>>
Envoyé : lundi 22 avril 2024 15:00
À : 'geoserver-users' 
mailto:geoserver-users@lists.sourceforge.net>>
Objet : [Geoserver-users] WMS broken after GeoServer Update (SAXException)

Hi,

I updated my GeoServer (Tomcat 9/Windows Server) from 2.24.2 to 2.25.0 and now 
I can't preview WMS layers. The error message is: 
"java.lang.reflect.UndeclaredThrowableExceptionorg.xml.sax.SAXException: Entity 
resolution disallowed for null". The same message is shown when I try to 
validate an SLD stylesheet. I copied the full stack trace to a file and 
attached it to this message. I also reverted back to the data dir included in 
the 2.25.0 release and can reproduce the error f.e. with the 'point' style.

I now found out that when I'm starting GeoServer with the 
-DENTITY_RESOLUTION_ALLOWLIST=* parameter, the error is gone. Although this 
parameter shouldn't be necessary because the styles are only containing 
references to www.opengis.net and 
www.w3.org which are in the default list of allowed domains 
for entity expansion according to the 
documentation.

The geoserver log shows a lot of "WARN   [geotools.xsd] - Sax parser property 
'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' not 
recognized.  Xerces version is incompatible." messages. Might there be a 
connection to the above issue?

Am I doing something wrong?

Thank you and best regards
Daniel
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] wms getmap with env variables

2024-04-22 Thread Giuseppe Falcone 
Hi to all,

I have a polygon layer and I want style it, in wms GetMap request, in
dynamic mode.
Polygons are identified by gid and at runtime I associate at every gid a
value. Polygon colors correspond to these values.
Therefore, I have this object:
[{1:15},{2:34},{3:57},] where 1,2,3 are the polygon gid and 15,34,57
are values necessary to color the polygons:
values between 0 and 20 -> color red
values between 21 and 40 -> color blue
...
I want to use variable substitution in sld, passing
[{1:15},{2:34},{3:57},] object with env parameter in getMap request,
but I can not read gid and values from env to build filter
propertyIsEqualTo (for gid) and valorize fill (with values)

Is this the right way? Any idea?
Thanks a lot.

Giuseppe
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] forwarding GEBCO WMS fails - help needed

2024-04-22 Thread Ian Turton 
It sounds like we (GeoTools) should accept `text/xml` especially when
requesting getCapabilities documents. But I'm really not sure 403 is the
correct response to not accepting the right content type.

Ian

On Mon, 22 Apr 2024 at 14:03, Peter Smythe  wrote:

> With access to Brent's GeoServer, I have managed to reproduce this
> problem, and it appears to be a combination of GeoTools HTTPClient (not
> MultithreadedHttpClient) and the GEBCO *MapServer* not allowing HTTP
> Header "accept": "text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2"
> for some reason.
>
> To reproduce:
> In Postman, GET
> https://wms.gebco.net/mapserv?REQUEST=GETCAPABILITIES&VERSION=1.3.0&SERVICE=WMS
> works fine, until the Accept header is changed from the default */* to 
> text/html,
> image/gif, image/jpeg, *; q=.2, */*; q=.2
> Returns 403 Unauthorised
>
> This Accept header appears to only be sent by GeoTools HTTPClient and is
> not sent by the GeoTools MultithreadedHttpClient, which is what I had on by
> default, when the cascaded WMS worked for me on my GeoServer (previous
> email):
>
> [image: image.png]
>  (in GeoServer New WMS Connection)
>
> Is this a GeoTools bug?  Or GeoServer?
>
> And then under what circumstances would the WMS data store fall back to
> the Simple HTTPClient rather than using the MultithreadedHttpClient (HTTP
> connection pooling), even if the above is ticked?
>
> Peter
>
> GeoServer PSC
> AWS Solutions Architect
> https://github.com/petersmythe
>
>
> On Sun, 21 Apr 2024 at 15:19, Peter Smythe  wrote:
>
>> Maybe try again, it works for me from GeoServer v2.25.0:
>>
>> [image: image.png]
>>
>> Peter
>>
>> GeoServer PSC
>> AWS Solutions Architect
>> https://github.com/petersmythe
>>
>>
>> On Sun, 21 Apr 2024 at 00:50, Brent Wood via Geoserver-users <
>> geoserver-users@lists.sourceforge.net> wrote:
>>
>>> Hi,
>>>
>>> I'm looking to install geoserver on a ship.
>>>
>>> I'd like to use the GEBCO WMS service to provide a background map layer,
>>> but cache it locally to avoid internet traffic.
>>>
>>> The capabilities doc is at:
>>>
>>> https://wms.gebco.net/mapserv?REQUEST=GETCAPABILITIES&VERSION=1.3.0&SERVICE=WMS
>>>
>>> The layer I wish to provide is: GEBCO_LATEST_SUB_ICE_TOPO
>>>
>>> I can connect & get the capabilities doc in a browser. I can select &
>>> open the layer in QGIS.
>>>
>>> When I try to set up a WMS store in Geoserver I enter the required
>>> parameters, but get told the connection test to the URL failed with error
>>> 403.
>>>
>>> I understand this means the Gebco server is refusing to reply with the
>>> doc. I'm not sure why the URL works from a browser but fails when sent from
>>> Geoserver, any suggestions appreciated, as far  as I know it is an
>>> identical request, from the same host.
>>>
>>>
>>> Thanks,
>>>
>>>   Brent Wood.
>>>
>>> ___
>>> Geoserver-users mailing list
>>>
>>> Please make sure you read the following two resources before posting to
>>> this list:
>>> - Earning your support instead of buying it, but Ian Turton:
>>> http://www.ianturton.com/talks/foss4g.html#/
>>> - The GeoServer user list posting guidelines:
>>> http://geoserver.org/comm/userlist-guidelines.html
>>>
>>> If you want to request a feature or an improvement, also see this:
>>> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>>>
>>>
>>> Geoserver-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>>
>> ___
> Geoserver-users mailing list
>
> Please make sure you read the following two resources before posting to
> this list:
> - Earning your support instead of buying it, but Ian Turton:
> http://www.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines:
> http://geoserver.org/comm/userlist-guidelines.html
>
> If you want to request a feature or an improvement, also see this:
> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>
>
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>


-- 
Ian Turton
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] forwarding GEBCO WMS fails - help needed

2024-04-22 Thread Peter Smythe 
With access to Brent's GeoServer, I have managed to reproduce this problem,
and it appears to be a combination of GeoTools HTTPClient (not
MultithreadedHttpClient) and the GEBCO *MapServer* not allowing HTTP Header
"accept": "text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2" for some
reason.

To reproduce:
In Postman, GET
https://wms.gebco.net/mapserv?REQUEST=GETCAPABILITIES&VERSION=1.3.0&SERVICE=WMS
works fine, until the Accept header is changed from the default */* to
text/html,
image/gif, image/jpeg, *; q=.2, */*; q=.2
Returns 403 Unauthorised

This Accept header appears to only be sent by GeoTools HTTPClient and is
not sent by the GeoTools MultithreadedHttpClient, which is what I had on by
default, when the cascaded WMS worked for me on my GeoServer (previous
email):

[image: image.png]
 (in GeoServer New WMS Connection)

Is this a GeoTools bug?  Or GeoServer?

And then under what circumstances would the WMS data store fall back to the
Simple HTTPClient rather than using the MultithreadedHttpClient (HTTP
connection pooling), even if the above is ticked?

Peter

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


On Sun, 21 Apr 2024 at 15:19, Peter Smythe  wrote:

> Maybe try again, it works for me from GeoServer v2.25.0:
>
> [image: image.png]
>
> Peter
>
> GeoServer PSC
> AWS Solutions Architect
> https://github.com/petersmythe
>
>
> On Sun, 21 Apr 2024 at 00:50, Brent Wood via Geoserver-users <
> geoserver-users@lists.sourceforge.net> wrote:
>
>> Hi,
>>
>> I'm looking to install geoserver on a ship.
>>
>> I'd like to use the GEBCO WMS service to provide a background map layer,
>> but cache it locally to avoid internet traffic.
>>
>> The capabilities doc is at:
>>
>> https://wms.gebco.net/mapserv?REQUEST=GETCAPABILITIES&VERSION=1.3.0&SERVICE=WMS
>>
>> The layer I wish to provide is: GEBCO_LATEST_SUB_ICE_TOPO
>>
>> I can connect & get the capabilities doc in a browser. I can select &
>> open the layer in QGIS.
>>
>> When I try to set up a WMS store in Geoserver I enter the required
>> parameters, but get told the connection test to the URL failed with error
>> 403.
>>
>> I understand this means the Gebco server is refusing to reply with the
>> doc. I'm not sure why the URL works from a browser but fails when sent from
>> Geoserver, any suggestions appreciated, as far  as I know it is an
>> identical request, from the same host.
>>
>>
>> Thanks,
>>
>>   Brent Wood.
>>
>> ___
>> Geoserver-users mailing list
>>
>> Please make sure you read the following two resources before posting to
>> this list:
>> - Earning your support instead of buying it, but Ian Turton:
>> http://www.ianturton.com/talks/foss4g.html#/
>> - The GeoServer user list posting guidelines:
>> http://geoserver.org/comm/userlist-guidelines.html
>>
>> If you want to request a feature or an improvement, also see this:
>> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>>
>>
>> Geoserver-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

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

2024-04-22 Thread Calliess Daniel Ing . 
Hi,

I updated my GeoServer (Tomcat 9/Windows Server) from 2.24.2 to 2.25.0 and now 
I can't preview WMS layers. The error message is: 
"java.lang.reflect.UndeclaredThrowableExceptionorg.xml.sax.SAXException: Entity 
resolution disallowed for null". The same message is shown when I try to 
validate an SLD stylesheet. I copied the full stack trace to a file and 
attached it to this message. I also reverted back to the data dir included in 
the 2.25.0 release and can reproduce the error f.e. with the 'point' style.

I now found out that when I'm starting GeoServer with the 
-DENTITY_RESOLUTION_ALLOWLIST=* parameter, the error is gone. Although this 
parameter shouldn't be necessary because the styles are only containing 
references to www.opengis.net and 
www.w3.org which are in the default list of allowed domains 
for entity expansion according to the 
documentation.

The geoserver log shows a lot of "WARN   [geotools.xsd] - Sax parser property 
'http://www.oracle.com/xml/jaxp/properties/entityExpansionLimit' not 
recognized.  Xerces version is incompatible." messages. Might there be a 
connection to the above issue?

Am I doing something wrong?

Thank you and best regards
Daniel


SAXException.log
Description: SAXException.log
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Setting SKIP_DEMO_DATA=true changes the global settings.

2024-04-22 Thread 西山 真吾 
Thanks for the reply.

I understood that it is normal.

Best regards,
Shingo

From: Andrea Aime 
Sent: Friday, April 19, 2024 7:30 PM
To: Shingo NISHIYAMA (西山 真吾) 
Cc: geoserver-users 
Subject: Re: [Geoserver-users] Setting SKIP_DEMO_DATA=true changes the global 
settings.

What you're seeing seems quite normal to me.
From the documentation:

"The environment variable SKIP_DEMO_DATA can be set to true to create an empty 
data directory."

So you switch from a demo data directory, that not only has data, but also 
several settings, to one that's
completely empty, where everything picks built-in defaults.

Using the internal data directory is anyways a bad idea, please externalize it 
instead,
 and use a
starter data directory with the base settings that best suit your needs. If you 
like the settings
found in the demo data, just start from there and remove the bits you don't 
want.


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 Fri, Apr 19, 2024 at 11:21 AM Shingo NISHIYAMA (西山 真吾) 
mailto:shin...@intent-exchange.com>> wrote:
Does anyone have any information?

Best regards,
Shingo

-Original Message-
From: Shingo NISHIYAMA
Sent: Friday, March 29, 2024 4:30 PM
To: geoserver-users 
mailto:geoserver-users@lists.sourceforge.net>>
Subject: Setting SKIP_DEMO_DATA=true changes the global settings.

Hello All,

I am using geoserver docker image.
If I set `SKIP_DEMO_DATA=true`[1], the Global Settings[2] will change.
For example, "Number of Decimals" is set to 4 instead of the default value of 8.

Is this an intended change? Or is it a bug?

[1] https://github.com/geoserver/docker?tab=readme-ov-file#environment-variables
[2] https://docs.geoserver.org/latest/en/user/configuration/globalsettings.html

$ docker image ls --digests 
docker.osgeo.org/geoserver
REPOSITORY   TAG   DIGEST   
 IMAGE ID   CREATED SIZE
docker.osgeo.org/geoserver   2.25.0
sha256:19335fcc02fbdcbcff0acdc89a05831f88e074d9025e49b11cb0355df1091c4f   
e2ab41d76027   9 days ago  957MB

$ docker run --rm -it -p 80:8080 -e SKIP_DEMO_DATA=false 
docker.osgeo.org/geoserver:2.25.0 ...
$ curl -s -u admin:geoserver http://localhost:80/geoserver/rest/settings | jq 
.global.settings.numDecimals
8

---

$ docker run --rm -it -p 80:8080 -e SKIP_DEMO_DATA=true 
docker.osgeo.org/geoserver:2.25.0 ...
$ curl -s -u admin:geoserver http://localhost:80/geoserver/rest/settings | jq 
.global.settings.numDecimals
4

Best regards,
Shingo



___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
___
Geoserver-users mailing list

Please make sure you read the following two resources before