On Jun 8, 8:32 am, William <[email protected]> wrote: > by "password protect" do you mean to stop unauthorized users from > downloading the kml files? > > I think in the API the KML is only accessed directly by Google > servers, so you might be able to set up a firewall whitelist to > restrict access to IP address ranges owned by Google.
This could be difficult to implement without locking out users from the web pages themselves. One solution could be to serve your KML via a script which accepted as much user-id verification as you wanted. The user could input a username and password into the page (using a Javascript prompt) which are then used in the URL to get the KML file. The script verifies the username and password and serves some KML -- either the full datafile requested or some dummy data if verification fails. A url such as serverscript.php? file=myfile.kml&username=me&password=that for example. Google's servers would pass the whole caboodle to your script and receive the kml back. Although username and password are in plain text, they only go between your user (who knows them), Google (who don't care) and your server (which needs them). -- You received this message because you are subscribed to the Google Groups "Google Maps API" 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-api?hl=en.
