Comment 3 for bug 406512

Pulled up wireshark to capture packets after a click on the "Authorize" button. RTM plugin, of course, sends data to api.rememberthemilk.com prior to bringing up a browser. Presumably, the response from the server is bad and so the RTM plugin never gets far enough to even attempt to bring up the browser. This appears to be what is happening.

I'm pasting only the important packets here, not all the syns and acks:

Outbound from RTM plugin:
POST /services/rest/?api_key=ee32c06f2d45baf935a2c046323457d8&method=rtm.auth.getFrob&api_sig=e8a1412173a1354198e93d96fc71bb5d

The reply:
HTTP/1.1 503 Service Temporarily Unavailable\r\n

I'm guessing this will clear itself up after a while? If RememberTheMilk.com gets it fixed on their side. It's be nice to have a bit more info from the plugin though, even if by debug. The right place for debug is in:

src/RtmNet/Rtm.cs in the else clause of AuthGetFrob.

If anyone wishes to follow the path:
start in AuthInit (note the error message there that you see when you click "Authorize" button on the 'gnome-do --debug' console):
http://bazaar.launchpad.net/~do-plugins/do-plugins/trunk/annotate/head%3A/RememberTheMilk/src/RTM.cs
to AuthGetFrob in:
http://bazaar.launchpad.net/~do-plugins/do-plugins/trunk/annotate/head%3A/RememberTheMilk/src/RtmNet/Rtm.cs