Awolola Ademola A.

Matric No:182477
CSC 776
World wide web is an information system of interlinked hypertext documents and other
digital resources that are accessed via the internet. It has become known simply as the web.
Internet is a global system of interconnected computer networks that use the standard
internet protocol suite (TCP/IP) to link several billion devices worldwide.
It is the interconnection of various networks that consists of millions of private, public,
academic, business and government networks of local to global scope, linked by a broad
array of electronic, wireless and optical networking technologies.
The internet is the hardware part- linked by a broad array of electronic, wireless and
optical networking technologies. While the world wide web is the software part which
depicts the collection of web pages connected together through hyperlinks and URLs.
The internet is governed by Internet Protocol- specifically dealing with data and their
transmission in packets while the world wide web is governed by hypertext transfer
protocol that deals with linking of files, documents and other resources of world wide
web.
World wide web is one of the services provided by the internet.
HTTP is a formal specification that defines the set of rules that governs the transfer of data
(in form of text, graphic images, sounds, video and other multimedia files) on the world wide
web. It is a protocol that provides a standard for web browser and servers to communicate.
HTTP clients (such as web browsers) and servers communicate via HTTP request and
response messages. HTTP is a simple request-response protocol that normally runs over TCP.
It specifies what messages clients may send to servers and what responses they get
back in return. The request and response headers are given in ASCII, just like in
SMTP. The three main HTTP message types are GET, POST and HEAD.
HTTP/1.1 addresses HTTP/1.0s shortcomings with increased flexibility in content handling
as well as advances in security and efficiency.
Version 1.1 of the protocol also made bandwidth optimization improvement to version
HTTP/1.0
HTTP/1.1 provide as much support as possible for future extensibility because of its
compatibility issue.
In HTTP/0.9 and 1.0 the connection is closed after a single/response pair. In HTTP/1.1 a
keep alive mechanism was introduced, where a connection could be reused for more than
one request latency perceptibly, because the client does not need to re-negotiate the TCP 3
way Handshake connection after the first request has been sent.
Caching: In HTTP/1.0, the limitation in caching causes semantic problem which happens due
to incorrect caching of some responses that should not have been cached. Also performance
problem due to failure to cache some responses that should have been cached.

In HTTP/1.1 terminology, a cache entry is fresh until it reaches its expiration time, at which
point it becomes stale. A cache need not discard a stale entry, but it normally must revalidate
it with the origin server before returning it in response to a subsequent request. However, the
protocol allows both origin servers and end-user clients to override this basic rule.
In HTTP/1.1, there is a better capability for Network connection management whereas
version 1.0 does not have enough capability thereby resulting in network congestion.
HTTP/1.1 solves the problem of arbitrary length in message transmission by introducing the
Chunked transfer-coding. The sender breaks the message body into chunks of arbitrary
length, and each chunk is sent with its length prepended; it marks the end of the message with
a zero-length chunk. The sender uses the Transfer-Encoding: chunked header to signal the use
of chunking. In HTTP/1.0, if the sender does not include a Content-Length header, the
recipient cannot tell if the message has been truncated due to transmission problems. This
ambiguity leads to errors, especially when truncated responses are stored in caches.
In Internet address conservation: the proliferation of vanity URLs in HTTP/1.0 causes a
proliferation of IP address allocations. Whereas version 1.1 overcomes the vanity URLs by
introduction of Host Header. HTTP/1.1 specification requires that an HTTP/1.1 server must
reject any HTTP/1.1 message that does not contain a Host header. The intent of the Host
header mechanism, and in particular the requirement that enforces its presence in HTTP/1.1
requests, is to speed the transition away from assigning a new IP address for every vanity
URL.
Error notification: HTTP/1.1 introduces a Warning header, which may carry any number of
subsidiary status indications. The intent is to allow a sender to advise the recipient that
something may be unsatisfactory about
an ostensibly successful response. Whereas HTTP/1.0 defined a relatively small set of sixteen
status codes, including the normal 200 (OK) code. Experience revealed the need for finer
resolution in error reporting.
Security, integrity, and authentication: HTTP/1.0 provides Basic Authentication and a
serious flaw in Basic authentication is that the username and password in the credentials are
unencrypted and therefore vulnerable to network snooping. The credentials also have no time
dependency, so they could be collected at leisure and used long after they were collected.
Whereas in HTTP/1.1, not only is the password no longer unencrypted, but the given
response is correct only for a single resource and method. It also support proxy authentication
through the introduction of proxy authenticate and proxy authorization header.
Content negotiation: HTTP/1.0 provided a few features to support content negotiation, but
RFC1945 [2] never uses that term and devotes less than a page to the relevant protocol
features. The HTTP/1.1 specification specifies these features with far greater care, and
introduces a number of new concepts. The goal of the content negotiation mechanism is to
choose the best available representation of a resource.