Using the Story Maps web page to create apps that uses Secure Sockets Layer (SSL) protocols for non-SSL-enabled organizations causes errors with mixed content from server services using Hypertext Transfer Protocol (HTTP).
上次发布: December 22, 2016No Product Found
漏洞 ID 编号
BUG-000098036
已提交
July 25, 2016
上次修改时间
June 5, 2024
适用范围
No Product Found
找到的版本
N/A
操作系统
Windows OS
操作系统版本
10.0
状态
Will Not Be Addressed
开发团队已考虑过该问题或请求,并决定不会解决该问题。 问题的“其他信息”部分可能包含进一步说明。
附加信息
We understand that in this instance an issue is encountered, however we are comfortable with our policy in this regard: If a member accesses the story maps website over HTTP and launches a builder it be over HTTP; if the website is accessed over HTTPS the builder will use HTTPS.
All ArcGIS Online organizations support HTTPS. Each organization has a setting that controls whether the organization *requires* the use of HTTPS when accessing maps and apps over the organizational URL (e.g., myorg.maps.arcgis.com).
There are two workarounds for this situation:
1) The best practice when working with any web content is to always use HTTPS URLs (when supported by the server) to prevent mixed content situations like this one. So the recommended workaround is to use HTTPS when adding layers to a web map.
2) Another workaround is to access the story maps site using HTTP.
解决办法
This is not a problem when creating the app from within the organization.