12-25-2018 07:09 PM - edited 12-25-2018 07:09 PM
I have a webmap SDK application that works fine when accessed by computer. The map that is generated is embedded in a frame. I can access the SDK map either directly (via gwmpub.aspx) or by displaying the page where i've embedded the map in an IFRAME> I am using Open Street Maps and a simple geomedia webmap publisher data source. When i try to display the map on a mobile phone, the URL changes automatcally from gwmpub.asxp to mobile.asxp which fine and all displays well. However if i access it through the webpage where it is embedded in an Iframe, i get a REQUEST NOT ALLOWED message in webmap and no map is displayed. The message appears 4 times - once for the intial map and then one time each for 3 different queries.
Is there some security issue involved on a mobile phone with embedding map in an IFRAME?
Solved! Go to Solution.
12-27-2018 01:21 AM
I suspect it's because of a specific task being done during map init which might not be understood by the Mobile.aspx for some reason. I suggest to create a test HTML with Mobile.aspx layout embedded and identical map configuration in place. Then you can debug it from your desktop.
12-27-2018 09:51 AM
I've simplified the problem -
This works fine on computer using either gwmpub.aspx or mobile.aspx
<iframe name="IncidentIframe" id="IncidentIframe" height="450" width=100% src="http://www.mywebsite.com/portalsdk4/mobile.aspx?gpm=9db2159d-85cb-4dc8-adff-73f3c0e8dab7&PlantStatus"></iframe>
On a cell phone, if i use mobile.aspx no map is generated and if i use gwmpub.aspx i get the REQUEST NOT ALLOWED messages
However on a cell phone, if i just go directly to the website
all works fine. So the only issue is using the iframe. I have tried with different browsers on mobile and get same results (chrome and firefox)
12-27-2018 11:18 AM
found the problem - you can't use location.href to test URL of an iframe on a mobile phone! I had code doing this in helloworld.js (testing one of the arguments in the webmap url)
3 weeks ago
location.href was not the problem. The problem was the browser choice. Safari (on iPhone) is the only browser that gives me the problem. We are using Chrome to successfully access the page via mobile phone.