In an Angular directive I'm trying to create an Information tool with OpenLayers 3 using the getGetFeatureInfoUrl method. I've set up a function which is using $http to return the info as JSON:

        scope.getinfo = function() {
            var wmsSource = new ol.source.TileWMS({
              url: 'http://xxxxxx.com:8080/geoserver/yyyy/wms',
              params: {'LAYERS': 'zzzzz'},
              serverType: 'geoserver'

            var wmsLayer = new ol.layer.Tile({
              source: wmsSource

            map.on('singleclick', function(evt) {
              //document.getElementById('info').innerHTML = '';
              var viewResolution = /** @type {number} */ (view.getResolution());
              var url = wmsSource.getGetFeatureInfoUrl(
                  evt.coordinate, viewResolution, 'EPSG:3857',
                  {'INFO_FORMAT': 'application/json',
                    'propertyName': 'formal_en'});
              if (url) {

                  var parser = new ol.format.GeoJSON();
                    url: url,
                    dataType: 'jsonp',
                    jsonpCallback: 'parseResponse'
                    }).then(function(response) {

                    var result = parser.readFeatures(response);
                    if (result.length) {
                        var info =[];
                        for (var i = 0, ii = result.length; i < ii; ++i) {


                         } else {
                             console.log('info else');
              } //

This is the error code from Console: Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://xxxxxx.com:8080/geoserver/yyyy/wms?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetFeatureInfo&FORMAT=image%2Fpng&TRANSPARENT=true&QUERY_LAYERS=zzzzz&LAYERS=zzzzz&INFO_FORMAT=application%2Fjsonp&propertyName=formal_en&I=34&J=135&WIDTH=256&HEIGHT=256&CRS=EPSG%3A3857&STYLES=&BBOX=-95393.41129989922%2C6826743.870205661%2C-94170.4188473364%2C6827966.862658224. (Reason: CORS header 'Access-Control-Allow-Origin' missing).

from what I understand I have to add a filter. I have tried adding this to end of C:\Program Files (x86)\GeoServer 2.9.0\webapps\geoserver\WEB-INF\web.xml


... and then restarting GeoServer but then GeoServer stopped working. Is this the correct way to fix the issue and if so am I editing web.xml correctly? Can anyone help please?

  • This question gis.stackexchange.com/questions/121555/… suggests you should use Jetty 7 and edit the jetty config rather than Geoserver: For GeoServer, you should avoid the default Jetty (version 6 too old, need to hack to set proper CORS headers) but use instead Jetty 7, TomCat or JBoss. not sure if it applies in you case – nmtoken Nov 23 '16 at 15:10
  • Thanks @nmtoken. I'm not sure what the default version of jetty is with Geoserver 2.9. Also if this is the issue then I will install Tomcat. Do you re-install Geoserver or can it just be configured to use Tomcat instead of Jetty? – Robert Nov 24 '16 at 11:19
  • I think you should be able to install Tomcat and configure it to handle GeoServer, there shouldn't be a need to uninstall GeoServer. – nmtoken Nov 24 '16 at 11:31