Twitter's Stream API is doing that chunked-encoding thing where it leaves the connection open, and the server streams content of unspecified size, Amos. Like, to avoid the latency with polling (which you just use the Twitter REST API to do). I think they keep their servers from getting swamped by limiting it to 1 open connection per userid. And I think I remember reading it only supports GET, not POST, if that matters (probably doesn't at the Squid level -- the chunked encoding is probably enough to kill it, no?). -----Original Message----- From: Zhe Chen [mailto:zhe@xxxxxxxx] Sent: Monday, November 22, 2010 5:07 PM To: Amos Jeffries Cc: squid-users@xxxxxxxxxxxxxxx Subject: EXTERNAL: Re: Does squid proxy server support Streaming response? I am using Twitter Stream API with Squid proxy server. The program will create a connnection with Twitter database, filter real time tweets and print them out. I cannot get any output when using Squid proxy server. > On 19/11/10 11:25, Zhe Chen wrote: >> Hi, >> >> Does squid proxy server support Streaming response? >> >> Thanks > > "Squid HTTP caching proxy" ... supports HTTP. > > Please explain this "Streaming response" you ask about? > > Amos > -- > Please be using > Current Stable Squid 2.7.STABLE9 or 3.1.9 > Beta testers wanted for 3.2.0.3 >
