search

chellymehdi / vopenlayers

Automatically exported from code.google.com/p/vopenlayers
0 stars 0 forks source link

Openlayer fetch using http causing mixed content warnings in IE #94

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
The issue we have is our clients are seeing lots of warning about mixed content 
(using IE in a domain with pretty hard security settings). We serve our website 
using ssl. I thought that changing google maps to ssl would solve the problem. 
However when I watch the page load via tamperdata, I see that there are still 
requests going to openlayers.org to get icons and stylesheets that are using 
http. I also see that openlayers only has an http website. So not sure that 
there is an easy answer to this problem.

Is it possible to use Vaadin7 to access openlayers directly? I saw something in 
the documentation that mentioned that javascript would be able to be done 
directly in Vaadin7. I haven't studied it yet, but would that be an option for 
solving this?

Original issue reported on code.google.com by paul.edw...@contextspace.com on 17 Oct 2012 at 9:13

GoogleCodeExporter commented 8 years ago 
Use the "non-hosted" widgetset and serve the OpenLayers.js script from your GWT 
module.

Overall instructions:
http://code.google.com/p/vopenlayers/wiki/Using

Example of such a setup, check lines 6 and 15. Also put OpenLayers.js into 
directory named "public", next to gwt module description file.
http://code.google.com/p/vopenlayers/source/browse/trunk/src/test/java/org/vaadi
n/vol/demo/VolExampleAppWidgetset.gwt.xml

This is actually often overall better setup as openlayers.org is sometimes 
under bit heavy load.

Original comment by ma...@vaadin.com on 17 Oct 2012 at 4:00

GoogleCodeExporter commented 8 years ago 
I also modified the Using wiki page to contain more details about using self 
hosted openlayers script.

Original comment by ma...@vaadin.com on 17 Oct 2012 at 4:06

GoogleCodeExporter commented 8 years ago 
Oh dear, I completely ignored that Vaadin7  part. 

Vaadin 7 uses cross site iframe linker in GWT -> cannot use script tags in 
gwt.xml files. Thus using custom javascript inclusion annotation provided by 
V7. We should either inject the script in more intelligent way or have two 
classes, one with the annotation one without. When using the one without 
developers should then inject the script by himself, one option would be the 
annotation).

Original comment by ma...@vaadin.com on 18 Oct 2012 at 6:05

GoogleCodeExporter commented 8 years ago 
Matti,

Thanks for your help. Thats got everything working. I can no longer see any 
http calls via tamperdata.

As for Vaadin7, think I'll probably need more detail when I get that far.

Original comment by paul.edw...@contextspace.com on 18 Oct 2012 at 6:28

GoogleCodeExporter commented 8 years ago

Original comment by ma...@vaadin.com on 16 Apr 2013 at 3:42