Why response from https://api.twitter.com/oauth2/token includes both Content-Length & Transfer-Encoding: chunked?


According to RFC: Messages MUST NOT include both a Content-Length header field and a non-identity transfer-coding.

I can’t see Transder-Encoding in e.g. Chrome Developer Console but the library i’m using loudly complains about it, also all online tools say you’re sending it.


We’re working to resolve this. Thanks for the report.