Comments on: Persistent Connections, Pipelining and Chunking http://www.subbu.org/blog/2004/11/persistent-connections-pipelining-and-chunking HTTP, REST and some Cycling Tue, 06 Jan 2009 21:55:34 +0000 http://wordpress.org/?v=2.7 hourly 1 By: Bakul http://www.subbu.org/blog/2004/11/persistent-connections-pipelining-and-chunking/comment-page-1#comment-8 Bakul Thu, 27 Sep 2007 09:09:20 +0000 http://wp.subbu.org/2004/11/persistent-connections-pipelining-and-chunking/#comment-8 Does HTTP RFC comment on the "host" field in the persistent HTTP connections? I am assuming that "host field will remain same for all GET requests on a persistent HTTP connection" Am I right in my assumption? thanks, Does HTTP RFC comment on the “host” field in the persistent HTTP connections?
I am assuming that “host field will remain same for all GET requests on a persistent HTTP connection”
Am I right in my assumption?
thanks,

]]> By: rag http://www.subbu.org/blog/2004/11/persistent-connections-pipelining-and-chunking/comment-page-1#comment-7 rag Mon, 29 Jan 2007 22:47:00 +0000 http://wp.subbu.org/2004/11/persistent-connections-pipelining-and-chunking/#comment-7 hi, i am raghu, i am impementing HTTP server using C,till persistent connection i hav finished, next pipelining need to be implemented ,so can u please tell the logic of how to implement pipelining in http server. hi,
i am raghu, i am impementing HTTP server using C,till persistent connection i hav finished, next pipelining need to be implemented ,so can u please tell the logic of how to implement pipelining in http server.

]]> By: Dheeraj Gautam http://www.subbu.org/blog/2004/11/persistent-connections-pipelining-and-chunking/comment-page-1#comment-6 Dheeraj Gautam Tue, 04 Apr 2006 06:21:12 +0000 http://wp.subbu.org/2004/11/persistent-connections-pipelining-and-chunking/#comment-6 Hi Subbu, Its a good overview of persistant connections. I have one query on this. What should be the behavior of HTTP/1.1 client if HTTP/1.1 Server doesn't include Connection header in response. Thanks in advance. Hi Subbu,

Its a good overview of persistant connections. I have one query on this. What should be the behavior of HTTP/1.1 client if HTTP/1.1 Server doesn’t include Connection header in response.

Thanks in advance.

]]> By: Vinay http://www.subbu.org/blog/2004/11/persistent-connections-pipelining-and-chunking/comment-page-1#comment-5 Vinay Wed, 03 Aug 2005 06:30:22 +0000 http://wp.subbu.org/2004/11/persistent-connections-pipelining-and-chunking/#comment-5 Hi Subbu, Can you give some sample code for Persistent connection on server side. I am trying to post Multiple requests by using HTTPURLConnection class. But after posting one request, i am not able to make second one. Thanx in Advance. Hi Subbu,
Can you give some sample code for Persistent connection on server side.
I am trying to post Multiple requests by using HTTPURLConnection class. But after posting one request, i am not able to make second one.
Thanx in Advance.

]]> By: Christopher Baus http://www.subbu.org/blog/2004/11/persistent-connections-pipelining-and-chunking/comment-page-1#comment-4 Christopher Baus Mon, 29 Nov 2004 19:37:47 +0000 http://wp.subbu.org/2004/11/persistent-connections-pipelining-and-chunking/#comment-4 Subbu, This is a good over view of how HTTP connection handling works. Having spent two years implementing an HTTP proxy, I can tell you this is not trivial. For instance Cisco had a buffer overflow problem because they weren't properly checking the max size of a chunk. The HTTP spec doesn't limit the size of a chunk, but most real world implementations must do this to prevent buffer overruns or other memory related failures. These are the implementation flaws that hackers love to take advantage of. Another interesting aspect of proxying is that there is basically two pipelines per client. One for the requests and one for the responses. If it is necessary to communicate between these two pipelines a queue must be used. This can get interesting quickly for features that seem simple at first glance, such as request logging. Subbu,

This is a good over view of how HTTP connection handling works. Having spent two years implementing an HTTP proxy, I can tell you this is not trivial. For instance Cisco had a buffer overflow problem because they weren’t properly checking the max size of a chunk. The HTTP spec doesn’t limit the size of a chunk, but most real world implementations must do this to prevent buffer overruns or other memory related failures. These are the implementation flaws that hackers love to take advantage of.

Another interesting aspect of proxying is that there is basically two pipelines per client. One for the requests and one for the responses. If it is necessary to communicate between these two pipelines a queue must be used. This can get interesting quickly for features that seem simple at first glance, such as request logging.

]]>