Thank you Chad, I decided to use an xml approach rather than kml to get around sending a kml to google first.
Thanks, Jared On 2010-10-27, at 11:21 PM, Chad Killingsworth wrote: > Ben Appleton outlined a strategy for handling this situation: > http://groups.google.com/group/google-maps-js-api-v3/browse_thread/thread/f824ed532e35da50/32c7023a9a57f0d7 > > Chad Killingsworth > > On Oct 27, 9:59 pm, Jared Cunningham <[email protected]> > wrote: >> I am creating an https service requiring login (have enterprise >> license) and am having some difficulty with kml overlays. I have buried >> my kmls in a non public location requiring login. I did not expect the >> data to be passed to google first, then the browser. Since google is >> unable to login to the site the kml is not passed and therefor not >> shown on the map. Any ideas how to get around this? >> >> Thanks in advance!! > > -- > 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. > -- 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.
