from https://github.com/openlayers/openlayers/blob/master/notes/2.12.md for Version 2.12 Especially when working with custom OSM tilesets from servers that do not send Access-Control-Allow-Origin headers, it is now necessary to configure the layer with tileOptions: {crossOriginKeyword: null}
Perhaps it is something similar. Arnd _____ Von: openlayers-users-boun...@lists.osgeo.org [mailto:openlayers-users-boun...@lists.osgeo.org] Im Auftrag von Peter Freimuth Gesendet: Freitag, 29. August 2014 08:40 An: openlayers-users@lists.osgeo.org Betreff: [OpenLayers-Users] problems with ol 2.11 and Cross Hi, we have a problem with a OSM tile service in Openlayers 2.11 which shall replace the google background map for an application in china as google map does not work. As the App is running with https we needed a https enabled tile service and received it from a german service provider. But in this application the Tile Service doesn't work due to the error: Image from origin 'https://tile.geofabrik.de' has been blocked from loading by Cross-Origin Resource Sharing policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://eyefind-ag-cn.blackbridge.com' is therefore not allowed access We can see the tiles being successfully loaded from the tile service in firebug but in the map we see only a bunch of broken image links. Its a standard OL OSM layer that works fine with outer test applications. Any hint on what might cause this problem is very, very welcome. Kind regards, Peter BlackBridge AG | Sitz Berlin | Amtsgericht Charlottenburg - Registergericht | HRB 152785 | Aufsichtsratsvorsitzender: David Westwood | Vorstand: Ryan Johnson --- Diese E-Mail ist frei von Viren und Malware, denn der avast! Antivirus Schutz ist aktiv. http://www.avast.com
_______________________________________________ Users mailing list us...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/openlayers-users
