On 2/3/22 9:21 AM, emmexx wrote: > I checked web.xml of geoserver and tomcat, server.xml of tomcat but I > couldn't find any meaningful difference between the 2 servers.
I found out what's the difference between the 2 setups: CORS. The production server had CORS enabled in conf/web.xml, the test server had not. I added the CORS filter to the conf/web.xml in the test server and I got the 403 Forbidden error there too. The problem arises only if cors.allowed.origins lists some domain, not when using * And it arises even with a fresh install of geoserver, it doesn't depend on my data. So I created a new instance of aws ec2 ami linux 64, installed tomcat, downloaded geoserver 2.20.2 war, installed it, tested if I could create a new layer (I can), added the cors filter to conf/web.xml and I can create a layer. I did the same with geoserver 2.19.0 with the same result. So there must be something wrong with my 2 centos servers. :-( I'll ask the system manager to setup a 3rd one. maxx _______________________________________________ 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