At the moment Chrome users will have a different experience than non-Chrome users, using the CloudMe.com Web Access service.

Google has recently updated its browser to version 19 and that has introduced a couple of issues that affect the CloudMe service.

1) When you are logging in, you will be asked for your username and password twice.
2) Uploading of files has been temporarily disabled with a workaround soon to be put in place.

These issues have been acknowledged by the Google/Chrome team and they are working on fixing them to make the Chrome browser work properly again. At the same time we at CloudMe are working on finding ways to work around these issues so the experience for our Chrome users will be as smooth as possible.

Keep reading for the techie explanation:

Issue 1 occurs because the Chrome-team has decided to disallow basic authentication embedded in request-URLs. As a side effect, by doing this, they also managed to break the Digest authentication that CloudMe uses. Credentials provided to XMLHTTPRequest will be ignored and the user will be asked of them instead. This issue is being tracked at:
http://code.google.com/p/chromium/issues/detail?id=123150

Issue 2 occurs when Chrome tries to upload a file and get a WWW-Authorization response as part of the Digest Authentication protocol. Chrome then tries to upload the file again with the correct credentials but at some point it forgets to “rewind” the file pointer and as a result will send a zero-filled file to the CloudMe-server. This issue is being tracked at:
http://groups.google.com/a/chromium.org/group/chromium-bugs/browse_thread/thread/15bc4992bcd4be1d