Talk:HTTP persistent connection

Computing Start‑class

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
Start	This article has been rated as Start-class on Wikipedia's content assessment scale.
???	This article has not yet received a rating on the project's importance scale.

Include a section on HTTP/1.0, keep-alive and proxy

There is no description of issues surrounding HTTP/1.0, keep-alive and proxy... Would be a good idea to introduce a section on this. —Preceding unsigned comment added by 75.30.227.252 (talk) 06:57, 1 June 2008 (UTC)[reply]

Can't get wikipedia to work

Keep getting "Proxy -- connection keep alive" inserted into text of article or discussion below where I was trying to edit.

When I make an edit, I get thrown to a page that says, basically that the edit failed.

Then I go back to the edit, click link at the top for "article" or "discussion," and my edit has been made after all.

And, I can never see the "Captcha" text.

I normally use FireFox on a Mac with OS X and NoScript (to protect against click-jacking, etc.) and the Little Snitch firewall and Apple firewall enabled,

Ports

How does this affect ports on the server and client? —Preceding unsigned comment added by 206.114.9.2 (talk) 19:35, 4 March 2009 (UTC)[reply]

Why isn't there an entry about the HTTP protocol for this feature? Connection: Keep-Alive —Preceding unsigned comment added by 76.178.152.104 (talk) 23:44, 7 October 2009 (UTC)[reply]

Chrome

All the others are talked about here, so I thought I would ask: could someone add in details on how Chrome handles persistent connections please? 130.179.26.134 (talk) 23:47, 18 May 2010 (UTC)[reply]

bad diagram

I think the timeline diagram in the section 'Use in web browsers' doensn't show what connection persistency is all about: Reducing the number of TCP communication cycles. The 'open' and 'close' events should be shown with visible handshake communication. This would clarify the benefits expected with connection persistency. — Preceding unsigned comment added by 85.182.86.242 (talk) 11:23, 23 December 2011 (UTC)[reply]

Clarify?

What exactly needs to be clarified about sending and receiving multiple requests and responses over a single TCP connection? --70.185.166.136 (talk) 04:28, 17 August 2012 (UTC)[reply]