Ответ

Sumo 04.10.2015 00:02 / 04.10.2015 00:09

Передается. Добавляем $.verbose(1) и видим:

> ./curl_headers.p
*   Trying 199.16.156.104...
* Connected to api.twitter.com (199.16.156.104) port 443 (#0)
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /usr/local/share/certs/ca-root-nss.crt
  CApath: none
* SSL connection using TLSv1.0 / AES128-SHA
* Server certificate:
* 	 subject: C=US; ST=California; L=San Francisco; O=Twitter, Inc.; OU=Twitter Security; CN=api.twitter.com
* 	 start date: 2014-08-03 00:00:00 GMT
* 	 expire date: 2016-12-31 23:59:59 GMT
* 	 subjectAltName: api.twitter.com matched
* 	 issuer: C=US; O=VeriSign, Inc.; OU=VeriSign Trust Network; OU=Terms of use at https://www.verisign.com/rpa (c)10; CN=VeriSign Class 3 Secure Server CA - G3
* 	 SSL certificate verify ok.
> POST /1.1/statuses/update.json HTTP/1.1
Host: api.twitter.com
Accept: */*
Authorization: aaa
Content-Length: 0
Content-Type: application/x-www-form-urlencoded

< HTTP/1.1 400 Bad Request
< content-length: 62
< content-type: application/json; charset=utf-8
< date: Sat, 03 Oct 2015 21:01:33 GMT
< server: tsa_b
< set-cookie: guest_id=v1%3A144390609343860325; Domain=.twitter.com; Path=/; Expires=Mon, 02-Oct-2017 21:01:33 UTC
< strict-transport-security: max-age=631138519
< x-connection-hash: 325522d8f7476bf2f2a0de524eafd015
< x-response-time: 4
* HTTP error before end of send, stop sending
<
* Closing connection 0

---