Discussion for 'Deprecating HTTP 1.0 for the Streaming API'


#1

Please use this discussion thread for any questions or comments about [node:17585, title=“Deprecating HTTP 1.0 for the Streaming API”].


#2

Probably a good idea to mention that sending a “Connection: close” header with the request will prevent the “Transfer-Encoding: chunked” in the response.

(My code was doing that and it took awhile for me to figure it out why my framework was interpreting the response as HTTP/1.0.)


#3

Good


#4

Update:

HTTP 1.0 will be deprecated on November 6, 2013 for User & Site Streams, and on January 6, 2013 for Firehose partners.


#5

Hello.
I have the same issue (twitter4j). Does it mean it is fine or should I modify the code to not send Connection: close header?


#6

Since around 2013-11-06 14:00 PST, the Twitter API search is regarding “gooブログ” (without quotes, no space) as two words, and hitting numerous entries.
It was treated correctly as one word before that time.

The search at: https://twitter.com/search-advanced takes “gooブログ” (without quotes, no space) as one word.

I see only change made for Twitter API on the day is “HTTP 1.0 will be deprecated on November 6, 2013 for User & Site Streams”, so it may be the case it is affecting on this issue.
Could you check if it is the case?


#7

I use libcurl © for getting access to https://userstream.twitter.com/1.1/user.json but since this morning I get: HTTP/1.0 400 Bad Request

Here is what I send: (logged with a server on my computer - the HOST part is correct in my normal request)

POST / HTTP/1.1
Host: 192.168.178.42:8787
Accept: /
Authorization: (should be correct)
Transfer-Encoding: chunked
Content-Type: application/x-www-form-urlencoded
Expect: 100-continue

Libcurl also returns error 43 - that is:
CURLE_BAD_FUNCTION_ARGUMENT (43)
Internal error. A function was called with a bad parameter.

Any ideas?