| Subject: | Support Google's optional redirect to SSL |
You can now set Google apps to require SSL for improved security. When that option is chosen,
and Net::Google::Calendar attempts to connect, it gets a 301-Permanently Moved response,
which Net::Google::Calendar then treats as a hard error and aborts.
There seems to be a Google bug involved: the redirect response does NOT point to an https URL;
instead it points to precisely the same URL that Net::Google::Calendar just tried to use. It would
be helpful to add some defensive code that does one or more of the following:
1) Specifically states that the new URL matches the old URL and Google must have a bug;
2) Warns that the problem might be that SSL is required;
3) Automatically retry with SSL before giving up.