https://community.esri.com/t5/arcgis-online-questions/no-access-control-allow-origin-header-arcgis/m-p/1352571#M56036 <P>We have a WMTS that is sourced from Geoserver that when loaded into ArcGIS Onlione we get the following response in the browser development console.</P><P>index.html:1 Access to fetch at '<A href="https://geos.oceanwise.eu/geoserver/gwc/service/wmts/1.0.0/WMTSCapabilities.xml" target="_blank" rel="noopener">https://geos.oceanwise.eu/geoserver/gwc/service/wmts/1.0.0/WMTSCapabilities.xml</A>' from origin '<A href="https://oceanwise.maps.arcgis.com" target="_blank" rel="noopener">https://oceanwise.maps.arcgis.com</A>' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.</P><P>The WMTS is&nbsp;<SPAN><SPAN class=""><A title="https://geos.oceanwise.eu/geoserver/gwc/service/wmts?" href="https://geos.oceanwise.eu/geoserver/gwc/service/wmts?" target="_blank" rel="noreferrer noopener">https://geos.oceanwise.eu/geoserver/gwc/service/wmts?</A></SPAN></SPAN></P><P>This service is used in other applications without issue including the Classic version of AGOL.&nbsp; What is it that AGOL is expecting from service that is not provided and causing this issue?</P> Wed, 22 Nov 2023 15:30:19 GMT CarolineLevey 2023-11-22T15:30:19Z https://community.esri.com/t5/arcgis-online-questions/no-access-control-allow-origin-header-arcgis/m-p/1352571#M56036 <P>We have a WMTS that is sourced from Geoserver that when loaded into ArcGIS Onlione we get the following response in the browser development console.</P><P>index.html:1 Access to fetch at '<A href="https://geos.oceanwise.eu/geoserver/gwc/service/wmts/1.0.0/WMTSCapabilities.xml" target="_blank" rel="noopener">https://geos.oceanwise.eu/geoserver/gwc/service/wmts/1.0.0/WMTSCapabilities.xml</A>' from origin '<A href="https://oceanwise.maps.arcgis.com" target="_blank" rel="noopener">https://oceanwise.maps.arcgis.com</A>' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.</P><P>The WMTS is&nbsp;<SPAN><SPAN class=""><A title="https://geos.oceanwise.eu/geoserver/gwc/service/wmts?" href="https://geos.oceanwise.eu/geoserver/gwc/service/wmts?" target="_blank" rel="noreferrer noopener">https://geos.oceanwise.eu/geoserver/gwc/service/wmts?</A></SPAN></SPAN></P><P>This service is used in other applications without issue including the Classic version of AGOL.&nbsp; What is it that AGOL is expecting from service that is not provided and causing this issue?</P> Wed, 22 Nov 2023 15:30:19 GMT https://community.esri.com/t5/arcgis-online-questions/no-access-control-allow-origin-header-arcgis/m-p/1352571#M56036 CarolineLevey 2023-11-22T15:30:19Z https://community.esri.com/t5/arcgis-online-questions/no-access-control-allow-origin-header-arcgis/m-p/1353495#M56082 <P>This link should help you out and getting the hosting server for the WMTS layer configured.</P><P><A href="https://developers.arcgis.com/javascript/latest/cors/" target="_blank">https://developers.arcgis.com/javascript/latest/cors/</A></P> Mon, 27 Nov 2023 14:47:07 GMT https://community.esri.com/t5/arcgis-online-questions/no-access-control-allow-origin-header-arcgis/m-p/1353495#M56082 RussRoberts 2023-11-27T14:47:07Z