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
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
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
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
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
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
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
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
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.
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
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
11 matches
Mail list logo
