<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Leaflet Geocoding and Chrome security update in Open Source Mapping Libraries Ques.</title>
    <link>https://community.esri.com/t5/open-source-mapping-libraries-ques/leaflet-geocoding-and-chrome-security-update/m-p/780373#M412</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks John, this clears things up.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 19 Apr 2016 14:09:58 GMT</pubDate>
    <dc:creator>TimWitt2</dc:creator>
    <dc:date>2016-04-19T14:09:58Z</dc:date>
    <item>
      <title>Leaflet Geocoding and Chrome security update</title>
      <link>https://community.esri.com/t5/open-source-mapping-libraries-ques/leaflet-geocoding-and-chrome-security-update/m-p/780371#M410</link>
      <description>&lt;P&gt;Hey everybody,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;With google chrome updating their security starting at version 50, as outlined &lt;A href="https://blogs.esri.com/esri/arcgis/2016/04/14/increased-web-api-security-in-google-chrome/" target="_blank"&gt;here&lt;/A&gt;​, I was wondering if the leaflet geocoding will be updated as well?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As for now, when I use arcgisOnline as the provider it uses an http url (see screenshot).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any input would be appreciated &lt;IMG src="https://community.esri.com/legacyfs/online/emoticons/happy.png" border="0" /&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Tim&lt;/P&gt;</description>
      <pubDate>Mon, 28 Aug 2023 13:29:31 GMT</pubDate>
      <guid>https://community.esri.com/t5/open-source-mapping-libraries-ques/leaflet-geocoding-and-chrome-security-update/m-p/780371#M410</guid>
      <dc:creator>TimWitt2</dc:creator>
      <dc:date>2023-08-28T13:29:31Z</dc:date>
    </item>
    <item>
      <title>Re: Leaflet Geocoding and Chrome security update</title>
      <link>https://community.esri.com/t5/open-source-mapping-libraries-ques/leaflet-geocoding-and-chrome-security-update/m-p/780372#M411</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;currently, the protocol used to make requests to ArcGIS Online's World Geocoding Service is inherited from what is used in your own application (ie: if you host over https, as will be required by Chrome 50 to leverage HTML5 Geolocation, geocoding requests will be encrypted too).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;that being said, if i'm understanding your suggestion correctly, it would be trivial (and probably helpful) for us to just hardcode https as the protocol instead of inheriting from the application.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;relevant source code is &lt;A href="https://github.com/Esri/esri-leaflet-geocoder/blob/master/src/EsriLeafletGeocoding.js#L2"&gt;here&lt;/A&gt;​.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Apr 2016 13:56:06 GMT</pubDate>
      <guid>https://community.esri.com/t5/open-source-mapping-libraries-ques/leaflet-geocoding-and-chrome-security-update/m-p/780372#M411</guid>
      <dc:creator>JohnGravois</dc:creator>
      <dc:date>2016-04-19T13:56:06Z</dc:date>
    </item>
    <item>
      <title>Re: Leaflet Geocoding and Chrome security update</title>
      <link>https://community.esri.com/t5/open-source-mapping-libraries-ques/leaflet-geocoding-and-chrome-security-update/m-p/780373#M412</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks John, this clears things up.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Apr 2016 14:09:58 GMT</pubDate>
      <guid>https://community.esri.com/t5/open-source-mapping-libraries-ques/leaflet-geocoding-and-chrome-security-update/m-p/780373#M412</guid>
      <dc:creator>TimWitt2</dc:creator>
      <dc:date>2016-04-19T14:09:58Z</dc:date>
    </item>
  </channel>
</rss>

