URLs to mark links as read are generating URI too large errors

[GoogleCodeExporter]

Operating System: Windows 7
Chrome version: 9.0.597.83 beta
Version of android2cloud Chrome extension: 2.0.2 / 2.0.3
The server I'm using: own
The Google Account name that I logged in with: private

What I am doing, step-by-step:
1. Go offline (shut down Chrome or the PC android2cloud is running on, or wait 
for issue #62 to disconnect android2cloud)
2. Send a few links via android2cloud
3. Go online (start Chrome / disable and re-enable extension, ...)
4. Queued links open.
5. Go offline again and back online.

What I expect to see:

Nothing should happen, no links were queued between steps 4 and 5.

What I see:

All the links that were opened in 4 open again after 5 (and every subsequent 
restart of the extension). The datastore shows the links as 'received = false'.

I also see this in Chrome's console:
links=%7B%22meta%22%3A%20%7B%22since_id%22%3A%20601005%2C%20%22links.latest%22%3
A%20633001%7D%2C%20%22links%22%3A%20%7B%22633001%22%3A%20%7B%22meta%22%3A%20%7B%
22since_id%22%3A%20633001%7D%2C%20%22link%22%3A%20%7B%22url%22%3A%20%22http%3A%5
C%2F%5C%2Fwww.facebook.com%5C%2[....]4%22%2C%20%22instance%22%3A%20%22all%22%2C%
20%22from%22%3A%20%22[....]5C%2FAndroid%29%22%2C%20%22id%22%3A%20633001%7D%7D%2C
%20%22621002%22%3A%20%7B%22meta%22%3A%20%7B%22since_id%22%3A%20621002%7D%2C%20%2
2link%22%3A%20%7B%22url%22%3A%20%22http%3A%5C%2F%5C%2F[........]%7D%7D%7D%7D&oau
th_consumer_key=dev.android2cloud.org&oauth_nonce=YxRVx&oauth_signature=3vyB%2Fn
EmAD5id2L%2B5jYVGvhkSfA%3D&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1296
461578&oauth_token=1%2F7sbat5k4EAEDscI5k-b9yJ3NruRzY1SL2lugVxfbfHQ
Failed to load resource: the server responded with a status of 414 (Request-URI 
Too Large)
functions.js:198marked link as read

It seems that the extension generates a GET request with a giant URI (contains 
all the URIs android2cloud opened + my account info) and this does not get 
accepted by the server.

Original issue reported on code.google.com by lev.ar...@gmail.com on 31 Jan 2011 at 8:23

[GoogleCodeExporter]

Thanks for this report. I'll fix the way links are marked as read, and release 
an update. Sorry about that.

If you'd like me to, I can remove the links that are opening for you from the 
database (just email me with the Device address, meaning email address and 
device name). Unfortunately, this does mean the links would be removed from the 
database. If not, this should be ready to update this week or early next.

Original comment by foran.pa...@gmail.com on 1 Feb 2011 at 9:38

• Changed title: URLs to mark links as read are generating URI too large errors
• Changed state: Accepted
• Added labels: OS-AppEngine

[GoogleCodeExporter]

Thanks for the update. No need to remove the links, I can do that on my own 
(using my own server so I got access to the datastore).

Original comment by lev.ar...@gmail.com on 1 Feb 2011 at 9:49

[GoogleCodeExporter]

Should be fixed in the 2.0.4 public beta. Would love confirmation on this. More 
information here: http://goo.gl/UvihB

Original comment by foran.pa...@gmail.com on 27 Feb 2011 at 9:59

• Changed state: InBeta

[GoogleCodeExporter]

I upgraded my appengine instance and Chrome extension yesterday evening and 
sent 6 links this morning before resetting the extension (it still hangs when 
the laptop gets suspended overnight). This seems to have worked as the links 
opened and are marked as received in the Data Store. I have to add though that 
there were no Facebook links among the ones I queued so I won't put my hand in 
fire just yet. (FB links shared from Tweetdeck always are about 3 miles long 
and thus more likely to trigger this issue than others.) I'll have to wait for 
my FB friends to share some site and video links to really test this, or 
rummage through the history to find some. Will keep you posted.

Original comment by lev.ar...@gmail.com on 28 Feb 2011 at 8:50

[GoogleCodeExporter]

Just tested a few longer links (one Facebook among them)... all got marked as 
received properly. I believe this is fixed.

Original comment by lev.ar...@gmail.com on 28 Feb 2011 at 1:40

[GoogleCodeExporter]

Awesome. I'll close this issue as soon as the upgrade leaves beta. Thanks for 
confirming it works now!

Original comment by foran.pa...@gmail.com on 28 Feb 2011 at 9:22

[GoogleCodeExporter]

Original comment by foran.pa...@gmail.com on 7 Mar 2011 at 8:40

• Changed state: Fixed