Web Search results for http - 1,150,000,000
This is the overview materials related to the W3C
HTTP activity, one of the W3C Architecture domain activities.
HTTP has been in use by the World Wide Web
...www.w3.org... Geolocation · eGovernment · GRDDL · Health Care and Life Sciences · HTML · HTML Tidy · HTML Validator ·
HTTP · Incubator · InkML · Internationalization
...www.w3.org
A free encyclopedia with millions of articles contributed collaboratively using Wiki software, in dozens of languages.
www.wikipedia.orgAbstract The Hypertext Transfer Protocol (
HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems.
...www.ietf.orgHowStuffWorks explains hundreds of subjects, from car engines to lock-picking to ESP, using clear language and tons of illustrations.
www.howstuffworks.comWelcome to Yahoo!, the world's most visited home page. Quickly find what you're searching for, get in touch with friends and stay in-the-know with the
...www.yahoo.comA midyear review of the initiatives underway at the all-volunteer Foundation showed that not only does the Apache
HTTP Server continue to be the world's
...www.apache.orgThe Apache
HTTP Server Project is an effort to develop and maintain an open- source
HTTP server for modern operating systems including UNIX and Windows NT.
...httpd.apache.org
Wikipedia
Hypertext Transfer Protocol
From Wikipedia, the free encyclopedia
(Redirected from Http)
The five-layer TCP/IP model
5. Application layer
DHCP · DNS · FTP · Gopher · HTTP · IMAP4 · IRC · NNTP · XMPP · POP3 · RTP · SIP · SMTP · SNMP · SSH · TELNET · RPC · RTCP · RTSP · TLS (and SSL) · SDP · SOAP · GTP · STUN · NTP · (more)
4. Transport layer
TCP · UDP · DCCP · SCTP · RSVP · ECN · (more)
3. Network/internet layer
IP (IPv4 · IPv6) · OSPF · IS-IS · BGP · IPsec · ARP · RARP · RIP · ICMP · ICMPv6 · IGMP · (more)
2. Data link layer
802.11 (WLAN) · 802.16 · Wi-Fi · WiMAX · ATM · DTM · Token ring · Ethernet · FDDI · Frame Relay · GPRS · EVDO · HSPA · HDLC · PPP · PPTP · L2TP · ISDN · ARCnet · LLTD · (more)
1. Physical layer
Ethernet physical layer · RS-232 · SONET/SDH · G.709 · Optical fiber · Coaxial cable · Twisted pair · (more)
This box: view • talk • edit
HTTP
Persistence · Compression · SSL
Headers
ETag · Cookie · Referer
Status codes
200 OK
301 Moved permanently
302 Found
403 Forbidden
404 Not Found
Hypertext Transfer Protocol (HTTP) is a communications protocol for the transfer of information on intranets and the World Wide Web. Its original purpose was to provide a way to publish and retrieve hypertext pages over the Internet.
HTTP development was coordinated by the World Wide Web Consortium (W3C) and the Internet Engineering Task Force (IETF), culminating in the publication of a series of Request for Comments (RFCs), most notably RFC 2616 (June 1999), which defines HTTP/1.1, the version of HTTP in common use.
HTTP is a request/response standard between a client and a server. A client is the end-user, the server is the web site. The client making an HTTP request - using a web browser, spider, or other end-user tool - is referred to as the user agent. The responding server - which stores or creates resources such as HTML files and images - is called the origin server. In between the user agent and origin server may be several intermediaries, such as proxies, gateways, and tunnels. HTTP is not constrained to using TCP/IP and its supporting layers, although this is its most popular application on the Internet. Indeed HTTP can be "implemented on top of any other protocol on the Internet, or on other networks. HTTP only presumes a reliable transport; any protocol that provides such guarantees can be used."
Typically, an HTTP client initiates a request. It establishes a Transmission Control Protocol (TCP) connection to a particular port on a host (port 80 by default; see List of TCP and UDP port numbers). An HTTP server listening on that port waits for the client to send a request message. Upon receiving the request, the server sends back a status line, such as "HTTP/1.1 200 OK", and a message of its own, the body of which is perhaps the requested file, an error message, or some other information.
The reason that HTTP uses TCP and not UDP is because much data must be sent for a webpage, and TCP provides transmission control, presents the data in order, and provides error correction. See the difference between TCP and UDP.
Resources to be accessed by HTTP are identified using Uniform Resource Identifiers (URIs) (or, more specifically, Uniform Resource Locators (URLs)) using the http: or https URI schemes.
Find more http info on Wikipedia
