Sorry that I’m reposting, but the message in the archive didn’t have any body text.
I’m in the middle of a prototype migration/deployment and have really hit a wall serving up my layers from geoserver. I’ve geoserver running from the “stand-alone” version running in jetty on one port and the webapp running in tomcat on another port. The webapp requests data from geoserver via localhost. This setup works fine on my laptop where I initially developed the prototype. Since moving everything to a server on the intranet, the webapp can request layers from geoserver, geoserver handles the request, and the webapp never gets anything returned. What’s even stranger, is if the prototype’s code is run a other hosts and requests data from the aforementioned geoserver, it gets data just fine. The webapp can successfully access remote WMS layers directly (not from, or cascaded by, my geoserver).
The laptop is running geoserver 2.3.0 and tomcat 7, both from an openSuSE 13.2 rpms, and Oracle’s java 1.7.0_79.
The server is running geoserver 2.7.2 (downloaded), and tomcat 7 and OpenJDK 1.7.0_85 from CentOS 7 rpms.
Sorry that I’m reposting, but the message in the archive didn’t have any body text.
I’m in the middle of a prototype migration/deployment and have really hit a wall serving up my layers from geoserver. I’ve geoserver running from the “stand-alone” version running in jetty on one port and the webapp running in tomcat on another port. The webapp requests data from geoserver via localhost. This setup works fine on my laptop where I initially developed the prototype. Since moving everything to a server on the intranet, the webapp can request layers from geoserver, geoserver handles the request, and the webapp never gets anything returned. What’s even stranger, is if the prototype’s code is run a other hosts and requests data from the aforementioned geoserver, it gets data just fine. The webapp can successfully access remote WMS layers directly (not from, or cascaded by, my geoserver).
The laptop is running geoserver 2.3.0 and tomcat 7, both from an openSuSE 13.2 rpms, and Oracle’s java 1.7.0_79.
The server is running geoserver 2.7.2 (downloaded), and tomcat 7 and OpenJDK 1.7.0_85 from CentOS 7 rpms.
Sorry that I’m reposting, but the message in the archive didn’t have any body text.
I’m in the middle of a prototype migration/deployment and have really hit a wall serving up my layers from geoserver. I’ve geoserver running from the “stand-alone” version running in jetty on one port and the webapp running in tomcat on another port. The webapp requests data from geoserver via localhost. This setup works fine on my laptop where I initially developed the prototype. Since moving everything to a server on the intranet, the webapp can request layers from geoserver, geoserver handles the request, and the webapp never gets anything returned. What’s even stranger, is if the prototype’s code is run a other hosts and requests data from the aforementioned geoserver, it gets data just fine. The webapp can successfully access remote WMS layers directly (not from, or cascaded by, my geoserver).
The laptop is running geoserver 2.3.0 and tomcat 7, both from an openSuSE 13.2 rpms, and Oracle’s java 1.7.0_79.
The server is running geoserver 2.7.2 (downloaded), and tomcat 7 and OpenJDK 1.7.0_85 from CentOS 7 rpms.
a) Set up a proxy - so geoserver appears to be served from your web server (this is why we have the base url setting in geoserver)
b) fiddle with CORS headers and allow cross domain scripting …
Sorry that I’m reposting, but the message in the archive didn’t have any body text.
I’m in the middle of a prototype migration/deployment and have really hit a wall serving up my layers from geoserver. I’ve geoserver running from the “stand-alone” version running in jetty on one port and the webapp running in tomcat on another port. The webapp requests data from geoserver via localhost. This setup works fine on my laptop where I initially developed the prototype. Since moving everything to a server on the intranet, the webapp can request layers from geoserver, geoserver handles the request, and the webapp never gets anything returned. What’s even stranger, is if the prototype’s code is run a other hosts and requests data from the aforementioned geoserver, it gets data just fine. The webapp can successfully access remote WMS layers directly (not from, or cascaded by, my geoserver).
The laptop is running geoserver 2.3.0 and tomcat 7, both from an openSuSE 13.2 rpms, and Oracle’s java 1.7.0_79.
The server is running geoserver 2.7.2 (downloaded), and tomcat 7 and OpenJDK 1.7.0_85 from CentOS 7 rpms.
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
Based on what I read so far, the best option is CORS. I guess that the change I’ve made in web.config is enough in the server side. I think I need now to create code in the client. If someone can help is going to be awesome.
I think I’ll need to take you up on the CORS info since I’ve not made any head way yet. Using tomcat’s org.apache.catalina.filters.CorsFilter filter didn’t work. I can get around the problem by specifying the URL to geoserver with the IP instead of localhost. We should probably continue outside the list, and I can post the solution when complete.
-B-
On Sep 2, 2015, at 11:06 AM, Jair Santos <jsantos5954@anonymised.com> wrote:
Hi Scott,
I’ve been replying to one person only all the time, and Jody keep remind me to reply to the list so everybody can follow and benefit from our research in the future. That’s my turn to remind someoneJ.
I’ll be very happy to work and share information about CORS, since it is an important piece of my work at this time.
Cheers.
JJ.
--- Let us all bask in television’s warm glowing warming glow ---
Scott Brunza 860.326.3637 scottso@anonymised.com
This e-mail and any files transmitted with it may be proprietary
and are intended solely for the use of the individual or entity
to whom they are addressed. If you have received this e-mail in
error, please notify the sender.
