On Wed, Aug 29, 2012 at 3:16 PM, Joseph Elfelt <[email protected]> wrote: >> Barry, > > > Do you have any insight whether we should be using https (instead of http) > to read the MyPLaces KML file? > I have tried doing so but that seems to make things worse.
In theory it shouldnt make a difference, can be used interchangably. In general not much point in https, because the content of the map is publically visible anyway. In the context of this issue, it doesnt seem to matter, it affects both http and https. > > Also, can you point me to a thread in the Google Maps community with > chatter about this? I took a look there but nothing jumped out. Well the first thread to note this is here: https://productforums.google.com/d/topic/maps/so_pZCg4b34/discussion And a fresh report today as the problem has resurfaced a few times. https://productforums.google.com/d/topic/maps/70uooPrHkxs/discussion but have been in contact privately with Google about it. > > -- > You received this message because you are subscribed to the Google Groups > "Google Maps JavaScript API v3" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-maps-js-api-v3/-/nqlZQ0RKvukJ. > > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-maps-js-api-v3?hl=en. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
