Update: Googling for the error message, I also find this:
The chunky-parser error message occurs when curl expects a chunked HTTP response body and then doesn t get one. Your reply sends the Transfer-Encoding: chunked
header, so curl expects to see a body chunked according to RFC2616 and it doesn t get one.
Obviously, a redirect shouldn t have a response body or even the Transfer-Encoding
header to begin with. You could try overriding the header, but maybe CouchDB inserts it unconditional in which case we should fix that, if you find out you can t override the Transfer-Encoding
header, can you file a bug report?
I have no idea what to make out of this in the context of fetching an arbitrary page, though.
Original post:
There s a CouchDB Bug report dealing with the same issue in conjunction with multi-byte data. Craigslist seems to run in ISO-8859-1, maybe the ad (or whatever you are fetching) has UTF-8 characters in it?