User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en; rv:184.108.40.206pre) Gecko/2008101800 Camino/2.0a1pre (like Firefox/3.0.4pre) Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en; rv:220.127.116.11pre) Gecko/2008101800 Camino/2.0a1pre (like Firefox/3.0.4pre) When I try to log in to my Picasa album account at Google site, an error page appears with the message "Bad Request - Your client has issued a malformed or illegal request." If I try Safari or Firefox, my log-in attempt succeeds without any problems. Reproducible: Always Steps to Reproduce: 1.Go to Google site. 2.Choose "Photos" under "More" at the top of the page. 3.Try to log in with one's account details. Actual Results: Google displays an error page with the message "Bad Request - Your client has issued a malformed or illegal request." Expected Results: Successful log in to one's account. Web page should open at "http://picasaweb.google.co.uk/home?hl=en&tab=wq"
This WFM (although I have a US-based Google account). What happens if you try using a fresh profile (http://pimpmycamino.com/parts/troubleshoot-camino can automate that process for you)?
Works fine here as well. Besides testing with Troubleshoot Camino, you could also clear your picassa cookies (the ones from picassaweb.google.co.uk).
Smokey Ardisson and philippe, thanks for the suggestions/comments. First, I tried Troubleshoot Camino, and my log in to Picasa Web Album account went successfully. Then, without Troubleshoot Camino, I cleared my cookies relating to picasa, but my log in attempt failed. After than, I tried 'Reset Camino...' menu command, and my log in was successful. I conclude then that my trouble in logging in to Picasa was something to do with my profile rather than a bug in Camino. Sorry to have taken your time. I'm new to these things, but I assume I should change the status of this case to 'Resolved'.
We'd like to have tracked it down to what specifically in your profile was triggering this to find out if there was a real bug here; unfortunately, resetting destroyed that information, so there's nothing more we can do.