geoserver xml header for cors xmlhttprequest

Question

I'm running geoserver-2.5.2. From an external server i would like to call it as a wfs source with ol3. For this I would like to allow this external server to access the data. It seams I need a header for cross-origin resource sharing (CORS). Like Zia has tried here, the link wasn't helpful to me as well, as geoserver didn't work anymore after editing the web.xml file the way as described in the link.

I believe I do need the access for calling the wfs data.

Answer 1

I know you post this question from along time but i'm just solve the problem.

I faced the same problem myself and i tried many solutions that discussed here or in other forums and finally i managed to solve the problem of enabling the Cross Origin in Geoserver.

After many trials i discovered that the solution is pretty simple following the exact steps that found in the Jetty webpage Jetty Cross Origin Filter.

But with a small change, the page said that we have to copy the following Cross-Origin filter to the (Web.xml) configuration file, but the solution that worked with me is copying this filter xml configuration in to (webdefault.xml) configuration file, when applying this change the geoserver worked like a charm and i could run any WFS, WMS GetFeatureInfoRequest in JSON format using AJAX instead of using IFrame soultion.

I'm using the following software versions:

• Boundless OpenGeo v4.5 .
• Geoserver v 2.6.2 .
• Jetty v 7.6.13.v20130916 .

Here is the detailed steps:

1. Download the matched version of the Jetty servlets according to your jetty version from this page Jetty Servlets .
2. In this example i'm using jetty v7.6.13.v20130916 so the jar file should be named
   (jetty-servlets-7.6.13.v20130916.jar) the filename will be different according to the jetty version - don't change its name because jetty matching the servlet name with its version like :
   jetty-servlets-<%JETTY_VERSION%>.jar, so don't rename it.

3. Stop the (GeoServer, Postgres) services and Take a copy from the OpenGeo directory located in
   (C:\Program Files (x86)\boundless\OpenGeo) and also Copy the OpenGeo directory located in
   (C:\ProgramData\boundless\OpenGeo) before starting this tutorial, as a precaution step.

4. Copy the file (jetty-servlets-7.6.13.v20130916.jar) (As-is) into the jetty Lib directory
   (*C:\Program Files (x86)\boundless\OpenGeo\jetty\lib*) also the directory may change according your installation directory.

5. Copy and paste the following xml lines into the (webdefault.xml) located in
   (C:\Program Files (x86)\boundless\OpenGeo\jetty\ect\webdefault.xml), i'm not sure that the location for these lines to place in the file is important or not but i paste them starting from line #306 after </serlet-mapping>.

<filter>
    <filter-name>cross-origin</filter-name>
    <filter-class>org.eclipse.jetty.servlets.CrossOriginFilter</filter-class>
</filter>
<filter-mapping>
    <filter-name>cross-origin</filter-name>
    <url-pattern>/*</url-pattern>
</filter-mapping>

6. Start the (GeoServer, Postgres) services, wait for a few seconds and browse to the geoserver page, the geoserver will start correctly.

This tutorial worked for me and i hope it work for anyone facing the same problem.

Answer 2

fwiw enable-cors.org is a great general resource for server or client configurations, in case you are deploying with Tomcat, for example.

Answer 3

Just to mention, Geoserver recently release 2.9-RC1, which comes with the more updated jetty (v9+) that supports CORS. Similar to the one mentioned by Ahmed GIS, you need to download the correct version of the jetty servlets. But this time, it is to copy into the directory "\WEB-INF\lib", and to edit the file "WEB-INF\web.xml" instead.

Answer 4

For GeoServer 2.8 I resolve by this procedure:

http://2carto.com/enable-cors-domain-geoserver-2-8/#comment-53

I tried implement to GeoServer 2.9 but can't resolve this problem so I re-installed GeoServer 2.8 and works.