Re: [mapguide-users] New builds of Fusion to support new Bing Maps
Thanks, it is still reporting those errors, but the real issue was a SSL setting in the browser (TLS 3) that was causing the issue. -- Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html ___ mapguide-users mailing list mapguide-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] New builds of Fusion to support new Bing Maps
Hi Gordon, I am not seeing these errors any more but I don't remember what fixed it. I wasn't clear in my explanation but I think the error was Bing related. Since that time we have gotten an API key. That may have fixed it. Also, it could be related to another issue we found. I put back the new fusion code which kept throwing errors but different ones than described I think. This turned out to be caused by having layers or folders in the map that were set to not show in the legend. Anyway, somewhere along the line the original error has disappeared. I hope somehow this helps you. On Tue., Nov. 6, 2018, 8:35 p.m. GordonL Did you still get these errors? > I am getting them in Chrome right now. I think there must be a IIS setting > change or a Chrome update.. > > > > > > -- > Sent from: > http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html > ___ > mapguide-users mailing list > mapguide-users@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/mapguide-users ___ mapguide-users mailing list mapguide-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] New builds of Fusion to support new Bing Maps
Did you still get these errors? I am getting them in Chrome right now. I think there must be a IIS setting change or a Chrome update.. -- Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html ___ mapguide-users mailing list mapguide-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapguide-users
Re: [mapguide-users] New builds of Fusion to support new Bing Maps
I have installed MGOS 3.1 and have applied the new Fusion code but I get 2 errors on the page load. fusionSF.js:1696 Refused to set unsafe header "Content-length" FusionSF.js:1697 Refused to set unsafe header "Connection" I do not get these errors with the original Fusion code. I am not currently using a Bing layer as we are in the process of getting our API key (enterprise). I don't know if these errors will disappear when Bing maps are added but it shouldn't throw an error without them. Ideas? -- Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html ___ mapguide-users mailing list mapguide-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapguide-users
