I added the cors filter to .../opengeo/geoserver/WEB-INF/web.xml.
After restarting tomcat geoserver is no more available and I get a 404 error page when loading the geoserver admin page.
The apache documentation says that the filter can be added in the tomcat config or in the application config. Is that right for geoserver?
Should I put the filter in a particular position inside the file?
I added the cors filter to .../opengeo/geoserver/WEB-INF/web.xml.
After restarting tomcat geoserver is no more available and I get a 404
error page when loading the geoserver admin page.
I've had success too with CORS in GeoServer using this CORS-filter: com.thetransactioncompany.cors.CORSFilter
I didn't want to rely on CORS support in Tomcat because maybe I want to use Jetty instead for some deployments.
--Steve
-----Original Message-----
From: emmexx [mailto:emmexx@anonymised.com]
Sent: Friday, October 31, 2014 2:03 AM
To: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Cors filter in geoserver web.xml crash
Il 10/30/2014 11:29 PM, emmexx scrisse:
I added the cors filter to .../opengeo/geoserver/WEB-INF/web.xml.
After restarting tomcat geoserver is no more available and I get a 404
error page when loading the geoserver admin page.