Thanks Emanuele.
Below is the WMTS GetCapabilites file I used to test the cascading wmts.
Hope this helps.
http://www.opengis.net/wmts/1.0"; xmlns:ows="
http://www.opengis.net/ows/1.1";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://
I resolved this issue by adding /wcs* to the "web" Filter Chain, which
includes "form" Authentication Filter. You can access this dialog in the
Web Administration interface under Security > Authentication > Filter Chains
> web. Perhaps it should be either noted or the underlying xml's changed if
Hi,
after updating GeoServer from 2.10.1 to 2.12-RC1 I'm experiencing the same
behaviour when POSTing to the REST API for seeding tiles in the integrated GWC.
Sending the xml document
workspace:layer
1445211.16687
Hi Mario,
> I can send my WMTS GetCapabilities
> xml used in the Store creation if required.
Yes, please, send any info that may help replicate your issue.
Cheers,
Emanuele
Alle 17:20:23 di Monday 16 October 2017, Mario Basa ha scritto:
> I am trying out now the new WMTS Cascading featur
Hi,
I created an issue for this so it doesn't get lost:
https://osgeo-org.atlassian.net/browse/GEOS-8356
Regards,
Nuno Oliveira
On 10/13/2017 01:52 PM, Jussila Ville wrote:
Hi,
I faced this problem as well. Is there an open ticket for this behavior? A
config flag in UI would be nice J
Te
