{
"subject": "Re: Content-Length header and 500 (was Re: Authentication, JSON RPC and Python)",
"content": {
"format": "html",
"body": "<div class=\"post\"><div class=\"quoteheader\"><a href=\"https://bitcointalk.org/index.php?topic=689.msg7299#msg7299\">Quote from: gavinandresen on August 03, 2010, 06:56:44 PM</a></div><div class=\"quote\"><div class=\"quoteheader\"><a href=\"https://bitcointalk.org/index.php?topic=689.msg7288#msg7288\">Quote from: jgarzik on August 03, 2010, 06:09:08 PM</a></div><div class=\"quote\">bitcoin requires the Content-Length header, but several JSON-RPC libraries do not provide it. When the Content-Length header is absent, bitcoin returns 500 Internal Server Error.<br/></div>Can you be more specific about which JSON libraries don't provide Content-Length ? It'd be nice to document that.<br/></div>I guess we should try to support the case where there's no Content-Length parameter. I don't want to rip and replace streams though, even if it has to read one character at a time.<br/><br/>Edit: That is, assuming there actually are any libraries that don't support Content-Length.</div>"
},
"source": {
"name": "Bitcoin Forum",
"url": "https://bitcointalk.org/index.php?topic=689.msg7335#msg7335"
},
"date": "2010-08-03T21:26:26Z"
}