dropbox crashed with KeyError in __getitem__(): 'content-length'

Same error on 11.04

:~$ dropbox start -i
Starting Dropbox...Traceback (most recent call last):
  File "/usr/bin/dropbox", line 250, in handle_ok
    self.download = DownloadState()
  File "/usr/bin/dropbox", line 157, in __init__
    self.size = int(self.file.info()['content-length'])
  File "/usr/lib/python2.7/rfc822.py", line 388, in __getitem__
    return self.dict[name.lower()]
KeyError: 'content-length'

Status changed to 'Confirmed' because the bug affects multiple users.

Same here.
After the upgrade from 11.04, Dropbox simply did not start, showing the same errors that you can see above.
I solved this by installing a previous version of Dropbox (dropbox_0.6.8_i386), and starting dropbox from the command line.
Regards
RN

Content-Length is a field that the Dropbox HTTP server returns in theory. If it's not there, it's not really a fault of the package...

$ HEAD http://www.dropbox.com/download?plat=lnx.x86
200 OK
Cache-Control: max-age=0
Connection: close
Date: Sat, 29 Oct 2011 14:16:38 GMT
Pragma: public
Accept-Ranges: bytes
Server: dbws
Content-Length: 16490475
Content-Type: application/x-tar
Client-Date: Sat, 29 Oct 2011 14:16:04 GMT
Client-Peer: 107.20.133.134:80
Client-Response-Num: 1
X-Robots-Tag: noindex,nofollow

As you see Content-Length is there...

This bug is related to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651065 and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651143

The real underlying problem is likely an intermediary proxy that refuses the download.

Therefore, this package should be more resilient if the network is not up yet.
When Ubuntu boots up, the wireless network may take several seconds to get activated. This is especially true when the router does not broadcast the SSID.

Mine works. It just throws the error (along with everything else at startup)