I propose moving this article to Hypertext Transfer Protocol, leaving a redirect from HTTP. (We should probably also add a redirect from http and maybe HyperText Transfer Protocol, too.) The naming conventions page doesn't explicitly address abbreviations, but it seems that using acronyms and abbreviations for article titles in general will lead to a great deal of confusion, even if HTTP is itself unambiguous. Anthony Argyriou 16:51, 23 October 2007 (CDT)
- Agreed, although I didn't do the moves before I did updates today. I also created an actual article about hypertext, rather than a redirect to HTML.Howard C. Berkowitz 11:57, 17 July 2008 (CDT)
- I see this move was not done; the full name is currently a redirect to HTTP. Is that as it should be? Sandy Harris 02:47, 12 September 2011 (UTC)
Is there a real web cache protocol expert in the house?
Is Cisco's WCCP the de facto standard, or is an IETF protocol such as ICP commonly used? Howard C. Berkowitz 11:57, 17 July 2008 (CDT)
note to self or another coming along to help out
Parts of the current article might appropriately be moved to World Wide Web, as they pertains to payloads of HTTP, rather than the protocol and how it works. If not moved, they should be under a special section designated "uses of the protocol" or some such.Pat Palmer 14:35, 12 June 2011 (UTC)
- A general note about status: I think this article needs a fair amount of organizating still. I hope to continue working on it, on and off, for the next few weeks, as I cannot see how to do it all in one day. Comments welcome of course, though it is not what I consider ready for review.Pat Palmer 22:04, 12 June 2011 (UTC)
- A reminder to myself or whomever: perhaps write a bit about how the GET method (with parameters in the URL) came into favor as so-called "REST" web services after year 2000.Pat Palmer 01:51, 10 September 2011 (UTC)
archived paragraph will be returned somewhere later
These sentences are only temporarily removed and should be re-added somewhere: The World Wide Web is more than HTML and HTTP alone. It includes a wide range of administrative techniques, performance-enhancing methods such as web caches and content distribution networks, and and has a robust caching system. HTTP works in the same manner if the users or servers are connected to the public Internet, an intranet, or an extranet. HTTP needs to be supplemented to provide security of the message transfer.
- ↑ Rescorla, E. (May 2000), HTTP Over TLS, Internet Engineering Task Force, RFC2818