Improving the security of Google APIs with SSL

We at Google go to great lengths to ensure every step is taken to protect our users’ data. As part of our ongoing effort to improve security everywhere, we will start requiring the use of SSL in many products. Requiring SSL improves security by encrypting data communications between users and Google, better protecting it from being intercepted by a malicious third party.

Some of these changes have already occurred. Many user-facing Google products now allow or require SSL, including encrypting Google web search, defaulting to SSL in Gmail, and requiring SSL in Google Docs. Next on our list is to improve SSL support for our developer facing APIs. For most APIs, our technical documentation, client libraries and code samples already use SSL. Many new APIs and versions will be SSL only. Further, the Google Maps API, which previously offered SSL only to Premier customers, is offering SSL to all developers starting today.

Additionally, beginning September 15, 2011, Google will require that all users of Google Documents List API, Google Spreadsheets API, and Google Sites API use SSL connections for all API requests. Specifically, this change will disallow all HTTP requests, responding with an HTTP 400 Bad Request response. API requests will only be accepted via HTTPS. For example, a request to http://docs.google.com/feeds/default/private/full will no longer pull a list of a user’s documents. Instead, a request must be made to https://docs.google.com/feeds/default/private/full.

This change should be transparent if you’re using the most recent version of the Google Data client libraries, since they already use SSL for all requests. If you’re not using the latest version, then please upgrade as soon as possible. If you’re not using our client libraries, then simply change any use of an HTTP URL to its corresponding HTTPS version in your code. Your existing OAuth and AuthSub tokens will continue to work using the HTTPS URLs, even if they were requested with a scope that uses an ‘http://’ scheme.

Although we’re initially requiring SSL for only a few APIs (those whose traffic was already mostly over SSL), we strongly recommend that you convert all your API clients as soon as possible to help protect your users’ data. Check the documentation for each API for more information about that API’s SSL support, including the updated Google Documents List API documentation, Google Spreadsheets API documentation, and Google Sites API documentation.

If you have any questions or concerns about this change, please follow up in the forums of the API you are using.

Battle of Britain – Bing Maps

World War Two: Battle of Britain Maps

“MSN has teamed up with Shoothill to present an interactive overview of the Battle of Britain. Zoom into a mosaic of archive images and documents; compare present-day maps with maps and charts showing bomb damage during the Blitz; and view high-resolution Photosynths of iconic RAF aircraft.”

Mapperz states:
“This is one of the ‘Best Bing Interactive Maps’ for 2010 (and 1940)”
World War Two: Battle of Britain Maps

The TimeMap is based on Bing Maps Silverlight Control. It shows original maps, reconnaissance imagery and target documents of the German Luftwaffe. You can navigate to various locations through quick links in a target list for London and Coventry.

  • The TimeScope can be dragged around to explore the location
  • The TimeSlider lets you switch between various historic maps and satellite imagery and the Documents.
  • DeepZoom – Compositions of the original target documents within the TimeScope.


Click for large view on the Map Controls, TimeSlider and TimeScope.

View the maps here:
http://news.uk.msn.com/in-depth/world-war-two/battle-of-britain/default.aspx

Editing your Google Docs on the go

Cross posted on the Official Google Blog, Google Enterprise Blog and the Google Docs Blog

With Google Docs, we’re always trying to make you more productive—and part of that means making it possible for you to get things done from anywhere, at anytime. That’s why we’re excited that the new documents editor now supports editing on your mobile browser. We’re rolling this out over the next few days.

That means that…

  • You can work on that important memo…while on the bus or train to work.
  • If you’re behind on a group proposal, but really want to make it to the ball game tonight, your whole team can work on it from the bleacher seats.
  • You can take minute-by-minute notes at a concert so you’ll always remember the setlist. And your friends can jealously follow in real-time at home.
  • …and the list goes on!

Take a look at this video to see mobile editing in action:

It’s easy to get started: visit docs.google.com in a browser on a supported device, and select the document you want to edit. Then, when you’re viewing it, press the Edit button to switch to the mobile editor.

In the next few days, we’re rolling this out to English-language users around the world on Android with Froyo (version 2.2) and on iOS devices (version 3.0+) including the iPad. We’ll be adding support for other languages soon. And as before, we also support editing of spreadsheets from your mobile device’s browser.

We hope you enjoy editing your documents on the go—especially when you’re at the game with a hot dog in your other hand.

Posted by: Andrew Grieve, Software Engineer