Hello Andrea,
We are not yet, but will be very soon. I am passing a header variable only
right now. But, as we get closer to production we will be using a couple of
methods of authentication.
Hopefully, I said that right.
Joe
On Mon, Sep 10, 2018, 11:31 AM Andrea Aime
wrote:
> Hi Torben,
>
Hi Torben,
looking at the original stackoverflow post, I believe the "bin" package is
used in this case, thus, Jetty.
Running on Tomcat for production is probably a better idea, though :-)
Another angle to look at might be the authentication configuration... is
the server allowing anonymous
Hello Joe,
I believe newer versions of Tomcat (8.5, 9.0) require slightly more strict
CORS configuration than older versions.
I have had some success with the following general configuration (on Tomcat
8.5):
CorsFilter
org.apache.catalina.filters.CorsFilter
cors.allowed.origins
*
Hi Joe,
question, do you have service security set up, so that GeoServer would
outright deny
a request unless the user making the request is authorized to?
E.g., something like denying any WFS request if the user does not have a
particular role?
Cheers
Andrea
On Mon, Sep 10, 2018 at 7:13 PM Joe
I'm not super up to speed on how you are using CORS. But i have it working
fine in my build. Please let me know how I can help..
Geoserver 2.13.2.war, Tomcat 9.0.7, Debian Docker Container.
Maybe just looking at my web.xml file would help?
Joe
On Mon, Sep 10, 2018, 10:05 AM Andrea Aime
Hi,
for the longest time CORS has been "not our problem", it's normally managed
in the web container (e.g., Tomcat, Jetty) or in
the eventual application fronting GeoServer (e.g., Apache, NGINX).
Maybe things have changed with the latest versions of Spring, if I search
for preflight test I find
Hello!
Daniele, yes, that's it. Somehow I couldn't find it by myself.
Simone, thank you for fixing!
пн, 10 сент. 2018 г. в 19:30, Simone Giannecchini <
simone.giannecch...@geo-solutions.it>:
> A fix is undergoing.
>
> Regards,
> Simone Giannecchini
> ==
> GeoServer Professional Services from
A fix is undergoing.
Regards,
Simone Giannecchini
==
GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information.
==
Ing. Simone Giannecchini
@simogeo
Founder/Director
GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584
Hi Sergey,
I think that you have hit the same problem I have found time ago:
https://osgeo-org.atlassian.net/browse/GEOS-7636
Is that the same bug?
Cheers,
Daniele
On Mon, Sep 10, 2018 at 5:06 PM, Sergey Kolosov
wrote:
> Hi Andrea,
>
> GeoServer 2.13.2.
> Legend (png file) is in the 'www'
So indeed in the end it was just the tomcat/conf/context.xml file that was
pointing to the psql database using the DNS of the old AWS instance, I
changed it and everything worked fine :)
Thanks!
--
Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html
Hi Andrea,
GeoServer 2.13.2.
Legend (png file) is in the 'www' directory in GEOSERVER_DATA_DIR.
Style is the default one.
Configuration:
https://drive.google.com/open?id=1Ntlg4WTpsEgKj5pm81Gb98ckoMHa1qZj
How to reproduce: I've created new data folder and copied default raster
style in the new
11 matches
Mail list logo
