![]() The Web's logo designed by Robert Cailliau |
|
Inventor | Tim Berners-Lee[1] Robert Cailliau |
---|---|
Company | CERN |
Availability | Worldwide |
Internet |
---|
![]() An Opte Project visualization of routing paths through a portion of the Internet
|
Services
|
![]() |
The World Wide Web (abbreviated as WWW or W3,[2] commonly known as the Web), is a system of interlinked hypertext documents accessed via the Internet. With a web browser, one can view web pages that may contain text, images, videos, and other multimedia, and navigate between them via hyperlinks.
Using concepts from his earlier hypertext systems like ENQUIRE, British engineer, computer scientist and at that time employee of CERN, Sir Tim Berners-Lee, now Director of the World Wide Web Consortium (W3C), wrote a proposal in March 1989 for what would eventually become the World Wide Web.[1] At CERN, a European research organisation near Geneva situated on Swiss and French soil,[3] Berners-Lee and Belgian computer scientist Robert Cailliau proposed in 1990 to use hypertext "to link and access information of various kinds as a web of nodes in which the user can browse at will",[4] and they publicly introduced the project in December of the same year.[5]
Contents |
History
![](https://web.archive.org/web/20130201194844im_/http://upload.wikimedia.org/wikipedia/commons/thumb/d/d1/First_Web_Server.jpg/220px-First_Web_Server.jpg)
In the May 1970 issue of Popular Science magazine, Arthur C. Clarke predicted that satellites would someday "bring the accumulated knowledge of the world to your fingertips" using a console that would combine the functionality of the photocopier, telephone, television and a small computer, allowing data transfer and video conferencing around the globe.[6]
In March 1989, Tim Berners-Lee wrote a proposal that referenced ENQUIRE, a database and software project he had built in 1980, and described a more elaborate information management system.[7]
With help from Robert Cailliau, he published a more formal proposal (on 12 November 1990) to build a "Hypertext project" called "WorldWideWeb" (one word, also "W3") as a "web" of "hypertext documents" to be viewed by "browsers" using a client–server architecture.[4] This proposal estimated that a read-only web would be developed within three months and that it would take six months to achieve "the creation of new links and new material by readers, [so that] authorship becomes universal" as well as "the automatic notification of a reader when new material of interest to him/her has become available." While the read-only goal was met, accessible authorship of web content took longer to mature, with the wiki concept, blogs, Web 2.0 and RSS/Atom.[8]
The proposal was modeled after the Dynatext SGML reader by Electronic Book Technology, a spin-off from the Institute for Research in Information and Scholarship at Brown University. The Dynatext system, licensed by CERN, was technically advanced and was a key player in the extension of SGML ISO 8879:1986 to Hypermedia within HyTime, but it was considered too expensive and had an inappropriate licensing policy for use in the general high energy physics community, namely a fee for each document and each document alteration.
![](https://web.archive.org/web/20130201194844im_/http://upload.wikimedia.org/wikipedia/commons/thumb/9/98/Cern_datacenter.jpg/220px-Cern_datacenter.jpg)
A NeXT Computer was used by Berners-Lee as the world's first web server and also to write the first web browser, WorldWideWeb, in 1990. By Christmas 1990, Berners-Lee had built all the tools necessary for a working Web:[9] the first web browser (which was a web editor as well); the first web server; and the first web pages,[10] which described the project itself. On 6 August 1991, he posted a short summary of the World Wide Web project on the alt.hypertext newsgroup.[11] This date also marked the debut of the Web as a publicly available service on the Internet. Many newsmedia have reported that the first photo on the web was uploaded by Berners-Lee in 1992, an image of the CERN house band Les Horribles Cernettes taken by Silvano de Gennaro; Gennaro has disclaimed this story, writing that media were "totally distorting our words for the sake of cheap sensationalism."[12] The first server outside Europe was set up at the Stanford Linear Accelerator Center (SLAC) in Palo Alto, California, to host the SPIRES-HEP database. Accounts differ substantially as to the date of this event. The World Wide Web Consortium says December 1992,[13] whereas SLAC itself claims 1991.[14][15] This is supported by a W3C document titled A Little History of the World Wide Web.[16]
The crucial underlying concept of hypertext originated with older projects from the 1960s, such as the Hypertext Editing System (HES) at Brown University, Ted Nelson's Project Xanadu, and Douglas Engelbart's oN-Line System (NLS). Both Nelson and Engelbart were in turn inspired by Vannevar Bush's microfilm-based "memex", which was described in the 1945 essay "As We May Think".[17]
Berners-Lee's breakthrough was to marry hypertext to the Internet. In his book Weaving The Web, he explains that he had repeatedly suggested that a marriage between the two technologies was possible to members of both technical communities, but when no one took up his invitation, he finally tackled the project himself. In the process, he developed three essential technologies:
- a system of globally unique identifiers for resources on the Web and elsewhere, the Universal Document Identifier (UDI), later known as Uniform Resource Locator (URL) and Uniform Resource Identifier (URI);
- the publishing language HyperText Markup Language (HTML);
- the Hypertext Transfer Protocol (HTTP).[18]
The World Wide Web had a number of differences from other hypertext systems that were then available. The Web required only unidirectional links rather than bidirectional ones. This made it possible for someone to link to another resource without action by the owner of that resource. It also significantly reduced the difficulty of implementing web servers and browsers (in comparison to earlier systems), but in turn presented the chronic problem of link rot. Unlike predecessors such as HyperCard, the World Wide Web was non-proprietary, making it possible to develop servers and clients independently and to add extensions without licensing restrictions. On 30 April 1993, CERN announced that the World Wide Web would be free to anyone, with no fees due.[19] Coming two months after the announcement that the server implementation of the Gopher protocol was no longer free to use, this produced a rapid shift away from Gopher and towards the Web. An early popular web browser was ViolaWWW for Unix and the X Windowing System.
![](https://web.archive.org/web/20130201194844im_/http://upload.wikimedia.org/wikipedia/commons/thumb/d/d3/Cailliau_Abramatic_Berners-Lee_10_years_WWW_consortium.png/220px-Cailliau_Abramatic_Berners-Lee_10_years_WWW_consortium.png)
Scholars generally agree that a turning point for the World Wide Web began with the introduction[20] of the Mosaic web browser[21] in 1993, a graphical browser developed by a team at the National Center for Supercomputing Applications at the University of Illinois at Urbana-Champaign (NCSA-UIUC), led by Marc Andreessen. Funding for Mosaic came from the U.S. High-Performance Computing and Communications Initiative and the High Performance Computing and Communication Act of 1991, one of several computing developments initiated by U.S. Senator Al Gore.[22] Prior to the release of Mosaic, graphics were not commonly mixed with text in web pages and the Web's popularity was less than older protocols in use over the Internet, such as Gopher and Wide Area Information Servers (WAIS). Mosaic's graphical user interface allowed the Web to become, by far, the most popular Internet protocol.
The World Wide Web Consortium (W3C) was founded by Tim Berners-Lee after he left the European Organization for Nuclear Research (CERN) in October 1994. It was founded at the Massachusetts Institute of Technology Laboratory for Computer Science (MIT/LCS) with support from the Defense Advanced Research Projects Agency (DARPA), which had pioneered the Internet; a year later, a second site was founded at INRIA (a French national computer research lab) with support from the European Commission DG InfSo; and in 1996, a third continental site was created in Japan at Keio University. By the end of 1994, while the total number of websites was still minute compared to present standards, quite a number of notable websites were already active, many of which are the precursors or inspiration for today's most popular services.
Connected by the existing Internet, other websites were created around the world, adding international standards for domain names and HTML. Since then, Berners-Lee has played an active role in guiding the development of web standards (such as the markup languages in which web pages are composed), and in recent years has advocated his vision of a Semantic Web. The World Wide Web enabled the spread of information over the Internet through an easy-to-use and flexible format. It thus played an important role in popularizing use of the Internet.[23] Although the two terms are sometimes conflated in popular use, World Wide Web is not synonymous with Internet.[24] The Web is a collection of documents and both client and server software using Internet protocols such as TCP/IP and HTTP. Tim Berners-Lee was knighted in 2004 by Queen Elizabeth II for his contribution to the World Wide Web.
Function
The terms Internet and World Wide Web are often used in everyday speech without much distinction. However, the Internet and the World Wide Web are not one and the same. The Internet is a global system of interconnected computer networks. In contrast, the Web is one of the services that runs on the Internet. It is a collection of text documents and other resources, linked by hyperlinks and URLs, usually accessed by web browsers from web servers. In short, the Web can be thought of as an application "running" on the Internet.[25]
Viewing a web page on the World Wide Web normally begins either by typing the URL of the page into a web browser or by following a hyperlink to that page or resource. The web browser then initiates a series of communication messages, behind the scenes, in order to fetch and display it. As an example, consider accessing a page with the URL http://example.org/wiki/World_Wide_Web .
First, the browser resolves the server-name portion of the URL (example.org) into an Internet Protocol address using the globally distributed database known as the Domain Name System (DNS); this lookup returns an IP address such as 208.80.152.2. The browser then requests the resource by sending an HTTP request across the Internet to the computer at that particular address. It makes the request to a particular application port in the underlying Internet Protocol Suite so that the computer receiving the request can distinguish an HTTP request from other network protocols it may be servicing such as e-mail delivery; the HTTP protocol normally uses port 80. The content of the HTTP request can be as simple as the two lines of text
GET /wiki/World_Wide_Web HTTP/1.1 Host: example.org
The computer receiving the HTTP request delivers it to web server software listening for requests on port 80. If the web server can fulfill the request it sends an HTTP response back to the browser indicating success, which can be as simple as
HTTP/1.0 200 OK Content-Type: text/html; charset=UTF-8
followed by the content of the requested page. The Hypertext Markup Language for a basic web page looks like
<html> <head> <title>Example.org – The World Wide Web</title> </head> <body> <p>The World Wide Web, abbreviated as WWW and commonly known ...</p> </body> </html>
The web browser parses the HTML, interpreting the markup (<title>, <p> for paragraph, and such) that surrounds the words in order to draw the text on the screen.
Many web pages use HTML to reference the URLs of other resources such as images, other embedded media, scripts that affect page behavior, and Cascading Style Sheets that affect page layout. The browser will make additional HTTP requests to the web server for these other Internet media types. As it receives their content from the web server, the browser progressively renders the page onto the screen as specified by its HTML and these additional resources.
Linking
Most web pages contain hyperlinks to other related pages and perhaps to downloadable files, source documents, definitions and other web resources. In the underlying HTML, a hyperlink looks like
<a href="http://example.org/wiki/Main_Page">Example.org, a free encyclopedia</a>
![](https://web.archive.org/web/20130201194844im_/http://upload.wikimedia.org/wikipedia/commons/thumb/b/b9/WorldWideWebAroundWikipedia.png/220px-WorldWideWebAroundWikipedia.png)
Such a collection of useful, related resources, interconnected via hypertext links is dubbed a web of information. Publication on the Internet created what Tim Berners-Lee first called the WorldWideWeb (in its original CamelCase, which was subsequently discarded) in November 1990.[4]
The hyperlink structure of the WWW is described by the webgraph: the nodes of the webgraph correspond to the web pages (or URLs) the directed edges between them to the hyperlinks.
Over time, many web resources pointed to by hyperlinks disappear, relocate, or are replaced with different content. This makes hyperlinks obsolete, a phenomenon referred to in some circles as link rot and the hyperlinks affected by it are often called dead links. The ephemeral nature of the Web has prompted many efforts to archive web sites. The Internet Archive, active since 1996, is the best known of such efforts.
Dynamic updates of web pages
JavaScript is a scripting language that was initially developed in 1995 by Brendan Eich, then of Netscape, for use within web pages.[26] The standardised version is ECMAScript.[26] To make web pages more interactive, some web applications also use JavaScript techniques such as Ajax (asynchronous JavaScript and XML). Client-side script is delivered with the page that can make additional HTTP requests to the server, either in response to user actions such as mouse movements or clicks, or based on lapsed time. The server's responses are used to modify the current page rather than creating a new page with each response, so the server needs only to provide limited, incremental information. Multiple Ajax requests can be handled at the same time, and users can interact with the page while data is being retrieved. Web pages may also regularly poll the server to check whether new information is available.[27]
WWW prefix
Many domain names used for the World Wide Web begin with www because of the long-standing practice of naming Internet hosts (servers) according to the services they provide. The hostname for a web server is often www, in the same way that it may be ftp for an FTP server, and news or nntp for a USENET news server. These host names appear as Domain Name System or [domain name server](DNS) subdomain names, as in www.example.com. The use of 'www' as a subdomain name is not required by any technical or policy standard and many web sites do not use it; indeed, the first ever web server was called nxoc01.cern.ch.[28] According to Paolo Palazzi,[29] who worked at CERN along with Tim Berners-Lee, the popular use of 'www' subdomain was accidental; the World Wide Web project page was intended to be published at www.cern.ch while info.cern.ch was intended to be the CERN home page, however the dns records were never switched, and the practice of prepending 'www' to an institution's website domain name was subsequently copied. Many established websites still use 'www', or they invent other subdomain names such as 'www2', 'secure', etc. Many such web servers are set up so that both the domain root (e.g., example.com) and the www subdomain (e.g., www.example.com) refer to the same site; others require one form or the other, or they may map to different web sites.
The use of a subdomain name is useful for load balancing incoming web traffic by creating a CNAME record that points to a cluster of web servers. Since, currently, only a subdomain can be used in a CNAME, the same result cannot be achieved by using the bare domain root.
When a user submits an incomplete domain name to a web browser in its address bar input field, some web browsers automatically try adding the prefix "www" to the beginning of it and possibly ".com", ".org" and ".net" at the end, depending on what might be missing. For example, entering 'microsoft' may be transformed to http://www.microsoft.com/ and 'openoffice' to http://www.openoffice.org. This feature started appearing in early versions of Mozilla Firefox, when it still had the working title 'Firebird' in early 2003, from an earlier practice in browsers such as Lynx.[30] It is reported that Microsoft was granted a US patent for the same idea in 2008, but only for mobile devices.[31]
In English, www is usually read as double-u double-u double-u. Some users pronounce it dub-dub-dub, particularly in New Zealand. Stephen Fry, in his "Podgrammes" series of podcasts, pronouncing it wuh wuh wuh. The English writer Douglas Adams once quipped in The Independent on Sunday (1999): "The World Wide Web is the only thing I know of whose shortened form takes three times longer to say than what it's short for". In Mandarin Chinese, World Wide Web is commonly translated via a phono-semantic matching to wàn wéi wǎng (万维网), which satisfies www and literally means "myriad dimensional net",[32] a translation that very appropriately reflects the design concept and proliferation of the World Wide Web. Tim Berners-Lee's web-space states that World Wide Web is officially spelled as three separate words, each capitalised, with no intervening hyphens.[33]
Use of the www prefix is declining as Web 2.0 web applications seek to brand their domain names and make them easily pronounceable.[34] As the mobile web grows in popularity, services like Gmail.com, MySpace.com, Facebook.com, Bebo.com and Twitter.com are most often discussed without adding www to the domain (or, indeed, the .com).
Scheme specifiers: http and https
The scheme specifier http:// or https:// at the start of a Web URI refers to Hypertext Transfer Protocol or HTTP Secure respectively. Unlike www, which has no specific purpose, these specify the communication protocol to be used for the request and response. The HTTP protocol is fundamental to the operation of the World Wide Web and the added encryption layer in HTTPS is essential when confidential information such as passwords or banking information are to be exchanged over the public Internet. Web browsers usually prepend http:// to addresses too, if omitted.
Web servers
The primary function of a web server is to deliver web pages on the request to clients. This means delivery of HTML documents and any additional content that may be included by a document, such as images, style sheets and scripts.
Privacy
Every time a web page is requested from a web server the server can identify, and usually it logs, the IP address from which the request arrived. Equally, unless set not to do so, most web browsers record the web pages that have been requested and viewed in a history feature, and usually cache much of the content locally. Unless HTTPS encryption is used, web requests and responses travel in plain text across the internet and they can be viewed, recorded and cached by intermediate systems.
When a web page asks for, and the user supplies, personally identifiable information such as their real name, address, e-mail address, etc., then a connection can be made between the current web traffic and that individual. If the website uses HTTP cookies, username and password authentication, or other tracking techniques, then it will be able to relate other web visits, before and after, to the identifiable information provided. In this way it is possible for a web-based organisation to develop and build a profile of the individual people who use its site or sites. It may be able to build a record for an individual that includes information about their leisure activities, their shopping interests, their profession, and other aspects of their demographic profile. These profiles are obviously of potential interest to marketeers, advertisers and others. Depending on the website's terms and conditions and the local laws that apply information from these profiles may be sold, shared, or passed to other organisations without the user being informed. For many ordinary people, this means little more than some unexpected e-mails in their in-box, or some uncannily relevant advertising on a future web page. For others, it can mean that time spent indulging an unusual interest can result in a deluge of further targeted marketing that may be unwelcome. Law enforcement, counter terrorism and espionage agencies can also identify, target and track individuals based on what appear to be their interests or proclivities on the web.
Social networking sites make a point of trying to get the user to truthfully expose their real names, interests and locations. This makes the social networking experience more realistic and therefore engaging for all their users. On the other hand, photographs uploaded and unguarded statements made will be identified to the individual, who may regret some decisions to publish these data. Employers, schools, parents and other relatives may be influenced by aspects of social networking profiles that the posting individual did not intend for these audiences. On-line bullies may make use of personal information to harass or stalk users. Modern social networking websites allow fine grained control of the privacy settings for each individual posting, but these can be complex and not easy to find or use, especially for beginners.[35]
Photographs and videos posted onto websites have caused particular problems, as they can add a person's face to an on-line profile. With modern and potential facial recognition technology, it may then be possible to relate that face with other, previously anonymous, images, events and scenarios that have been imaged elsewhere. Because of image caching, mirroring and copying, it is difficult to remove an image from the World Wide Web.
Intellectual property
The intellectual property rights for any creative work initially rests with its creator. Web users who want to publish their work onto the World Wide Web, however, need to be aware of the details of the way they do it. If artwork, photographs, writings, poems, or technical innovations are published by their creator onto a privately owned web server, then they may choose the copyright and other conditions freely themselves. This is unusual though; more commonly work is uploaded to web sites and servers that are owned by other organizations. It depends upon the terms and conditions of the site or service provider to what extent the original owner automatically signs over rights to their work by the choice of destination and by the act of uploading.[citation needed]
Many users of the web erroneously assume that everything they may find on line is freely available to them as if it was in the public domain. This is almost never the case, unless the web site publishing the work clearly states that it is. On the other hand, content owners are aware of this widespread belief, and expect that sooner or later almost everything that is published will probably be used in some capacity somewhere without their permission. Many publishers therefore embed visible or invisible digital watermarks in their media files, sometimes charging users to receive unmarked copies for legitimate use. Digital rights management includes forms of access control technology that further limit the use of digital content even after it has been bought or downloaded.[citation needed]
Security
The Web has become criminals' preferred pathway for spreading malware. Cybercrime carried out on the Web can include identity theft, fraud, espionage and intelligence gathering.[36] Web-based vulnerabilities now outnumber traditional computer security concerns,[37][38] and as measured by Google, about one in ten web pages may contain malicious code.[39] Most Web-based attacks take place on legitimate websites, and most, as measured by Sophos, are hosted in the United States, China and Russia.[40] The most common of all malware threats is SQL injection attacks against websites.[41] Through HTML and URIs the Web was vulnerable to attacks like cross-site scripting (XSS) that came with the introduction of JavaScript[42] and were exacerbated to some degree by Web 2.0 and Ajax web design that favors the use of scripts.[43] Today by one estimate, 70% of all websites are open to XSS attacks on their users.[44]
Proposed solutions vary to extremes. Large security vendors like McAfee already design governance and compliance suites to meet post-9/11 regulations,[45] and some, like Finjan have recommended active real-time inspection of code and all content regardless of its source.[36] Some have argued that for enterprise to see security as a business opportunity rather than a cost center,[46] "ubiquitous, always-on digital rights management" enforced in the infrastructure by a handful of organizations must replace the hundreds of companies that today secure data and networks.[47] Jonathan Zittrain has said users sharing responsibility for computing safety is far preferable to locking down the Internet.[48]
Standards
Many formal standards and other technical specifications and software define the operation of different aspects of the World Wide Web, the Internet, and computer information exchange. Many of the documents are the work of the World Wide Web Consortium (W3C), headed by Berners-Lee, but some are produced by the Internet Engineering Task Force (IETF) and other organizations.
Usually, when web standards are discussed, the following publications are seen as foundational:
- Recommendations for markup languages, especially HTML and XHTML, from the W3C. These define the structure and interpretation of hypertext documents.
- Recommendations for stylesheets, especially CSS, from the W3C.
- Standards for ECMAScript (usually in the form of JavaScript), from Ecma International.
- Recommendations for the Document Object Model, from W3C.
Additional publications provide definitions of other essential technologies for the World Wide Web, including, but not limited to, the following:
- Uniform Resource Identifier (URI), which is a universal system for referencing resources on the Internet, such as hypertext documents and images. URIs, often called URLs, are defined by the IETF's RFC 3986 / STD 66: Uniform Resource Identifier (URI): Generic Syntax, as well as its predecessors and numerous URI scheme-defining RFCs;
- HyperText Transfer Protocol (HTTP), especially as defined by RFC 2616: HTTP/1.1 and RFC 2617: HTTP Authentication, which specify how the browser and server authenticate each other.
Accessibility
There are methods available for accessing the web in alternative mediums and formats, so as to enable use by individuals with disabilities. These disabilities may be visual, auditory, physical, speech related, cognitive, neurological, or some combination therin. Accessibility features also help others with temporary disabilities like a broken arm or the aging population as their abilities change.[49] The Web is used for receiving information as well as providing information and interacting with society. The World Wide Web Consortium claims it essential that the Web be accessible in order to provide equal access and equal opportunity to people with disabilities.[50] Tim Berners-Lee once noted, "The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect."[49] Many countries regulate web accessibility as a requirement for websites.[51] International cooperation in the W3C Web Accessibility Initiative led to simple guidelines that web content authors as well as software developers can use to make the Web accessible to persons who may or may not be using assistive technology.[49][52]
Internationalization
The W3C Internationalization Activity assures that web technology will work in all languages, scripts, and cultures.[53] Beginning in 2004 or 2005, Unicode gained ground and eventually in December 2007 surpassed both ASCII and Western European as the Web's most frequently used character encoding.[54] Originally RFC 3986 allowed resources to be identified by URI in a subset of US-ASCII. RFC 3987 allows more characters—any character in the Universal Character Set—and now a resource can be identified by IRI in any language.[55]
Statistics
Between 2005 and 2010, the number of Web users doubled, and was expected to surpass two billion in 2010.[56] Early studies in 1998 and 1999 estimating the size of the web using capture/recapture methods showed that much of the web was not indexed by search engines and the web was much larger than expected.[57][58] According to a 2001 study, there were a massive number, over 550 billion, of documents on the Web, mostly in the invisible Web, or Deep Web.[59] A 2002 survey of 2,024 million Web pages[60] determined that by far the most Web content was in the English language: 56.4%; next were pages in German (7.7%), French (5.6%), and Japanese (4.9%). A more recent study, which used Web searches in 75 different languages to sample the Web, determined that there were over 11.5 billion Web pages in the publicly indexable Web as of the end of January 2005.[61] As of March 2009, the indexable web contains at least 25.21 billion pages.[62] On 25 July 2008, Google software engineers Jesse Alpert and Nissan Hajaj announced that Google Search had discovered one trillion unique URLs.[63] As of May 2009, over 109.5 million domains operated.[64][not in citation given] Of these 74% were commercial or other sites operating in the .com
generic top-level domain.[64]
Statistics measuring a website's popularity are usually based either on the number of page views or on associated server 'hits' (file requests) that it receives.
Speed issues
Frustration over congestion issues in the Internet infrastructure and the high latency that results in slow browsing has led to a pejorative name for the World Wide Web: the World Wide Wait.[65] Speeding up the Internet is an ongoing discussion over the use of peering and QoS technologies. Other solutions to reduce the congestion can be found at W3C.[66] Guidelines for Web response times are:[67]
- 0.1 second (one tenth of a second). Ideal response time. The user does not sense any interruption.
- 1 second. Highest acceptable response time. Download times above 1 second interrupt the user experience.
- 10 seconds. Unacceptable response time. The user experience is interrupted and the user is likely to leave the site or system.
Caching
If a user revisits a Web page after only a short interval, the page data may not need to be re-obtained from the source Web server. Almost all web browsers cache recently obtained data, usually on the local hard drive. HTTP requests sent by a browser will usually ask only for data that has changed since the last download. If the locally cached data are still current, they will be reused. Caching helps reduce the amount of Web traffic on the Internet. The decision about expiration is made independently for each downloaded file, whether image, stylesheet, JavaScript, HTML, or other resource. Thus even on sites with highly dynamic content, many of the basic resources need to be refreshed only occasionally. Web site designers find it worthwhile to collate resources such as CSS data and JavaScript into a few site-wide files so that they can be cached efficiently. This helps reduce page download times and lowers demands on the Web server.
There are other components of the Internet that can cache Web content. Corporate and academic firewalls often cache Web resources requested by one user for the benefit of all. (See also caching proxy server.) Some search engines also store cached content from websites. Apart from the facilities built into Web servers that can determine when files have been updated and so need to be re-sent, designers of dynamically generated Web pages can control the HTTP headers sent back to requesting users, so that transient or sensitive pages are not cached. Internet banking and news sites frequently use this facility. Data requested with an HTTP 'GET' is likely to be cached if other conditions are met; data obtained in response to a 'POST' is assumed to depend on the data that was POSTed and so is not cached.
See also
References
- ^ a b Quittner, Joshua (29 March 1999). "Tim Berners Lee – Time 100 People of the Century". Time Magazine. http://www.time.com/time/magazine/article/0,9171,990627,00.html. Retrieved 17 May 2010. "He wove the World Wide Web and created a mass medium for the 21st century. The World Wide Web is Berners-Lee's alone. He designed it. He loosed it on the world. And he more than anyone else has fought to keep it open, nonproprietary and free. ."
- ^ "World Wide Web Consortium". http://www.w3.org/. "The World Wide Web Consortium (W3C)..."
- ^ Le Web a été inventé... en France ! – Le Point
- ^ a b c "Berners-Lee, Tim; Cailliau, Robert (12 November 1990). "WorldWideWeb: Proposal for a hypertexts Project". http://w3.org/Proposal.html. Retrieved 27 July 2009.
- ^ Berners-Lee, Tim. "Pre-W3C Web and Internet Background". World Wide Web Consortium. http://w3.org/2004/Talks/w3c10-HowItAllStarted/?n=15. Retrieved 21 April 2009.
- ^ von Braun, Wernher (May 1970). "TV Broadcast Satellite". Popular Science: 65–66. http://www.popsci.com/archive-viewer?id=8QAAAAAAMBAJ&pg=66&query=a+c+clarke. Retrieved 12 January 2011.
- ^ Berners-Lee, Tim (March 1989). "Information Management: A Proposal". W3C. http://w3.org/History/1989/proposal.html. Retrieved 27 July 2009.
- ^ "Tim Berners-Lee's original World Wide Web browser". http://info.cern.ch/NextBrowser.html. "With recent phenomena like blogs and wikis, the web is beginning to develop the kind of collaborative nature that its inventor envisaged from the start."
- ^ "Tim Berners-Lee: client". W3.org. http://w3.org/People/Berners-Lee/WorldWideWeb. Retrieved 27 July 2009.
- ^ "First Web pages". W3.org. http://w3.org/History/19921103-hypertext/hypertext/WWW/TheProject.html. Retrieved 27 July 2009.
- ^ "Short summary of the World Wide Web project". Google. 6 August 1991. http://groups.google.com/group/alt.hypertext/msg/395f282a67a1916c. Retrieved 27 July 2009.
- ^ "Silvano de Gennaro disclaims 'the first photo on the web'". http://musiclub.web.cern.ch/MusiClub/bands/cernettes/disclaimer.html. Retrieved 27 July 2012. "If you read well our website, it says that it was, to our knowledge, the 'first photo of a band'. Dozens of media are totally distorting our words for the sake of cheap sensationalism. Nobody knows which was the first photo on the web."
- ^ "W3C timeline". http://w3.org/2005/01/timelines/timeline-2500x998.png. Retrieved 30 March 2010.
- ^ "About SPIRES". http://slac.stanford.edu/spires/about/. Retrieved 30 March 2010.
- ^ "The Early World Wide Web at SLAC". http://www.slac.stanford.edu/history/earlyweb/history.shtml.
- ^ "A Little History of the World Wide Web". http://www.w3.org/History.html.
- ^ Conklin, Jeff (1987), IEEE Computer 20 (9): 17–41
- ^ "Inventor of the Week Archive: The World Wide Web". Massachusetts Institute of Technology: MIT School of Engineering. http://web.mit.edu/invent/iow/berners-lee.html. Retrieved 23 July 2009.
- ^ "Ten Years Public Domain for the Original Web Software". Tenyears-www.web.cern.ch. 30 April 2003. http://tenyears-www.web.cern.ch/tenyears-www/Welcome.html. Retrieved 27 July 2009.
- ^ "Mosaic Web Browser History – NCSA, Marc Andreessen, Eric Bina". Livinginternet.com. http://livinginternet.com/w/wi_mosaic.htm. Retrieved 27 July 2009.
- ^ "NCSA Mosaic – September 10, 1993 Demo". Totic.org. http://totic.org/nscp/demodoc/demo.html. Retrieved 27 July 2009.
- ^ "Vice President Al Gore's ENIAC Anniversary Speech". Cs.washington.edu. 14 February 1996. http://cs.washington.edu/homes/lazowska/faculty.lecture/innovation/gore.html. Retrieved 27 July 2009.
- ^ "Internet legal definition of Internet". West's Encyclopedia of American Law, edition 2. Free Online Law Dictionary. 15 July 2009. http://legal-dictionary.thefreedictionary.com/Internet. Retrieved 25 November 2008.
- ^ "WWW (World Wide Web) Definition". TechTerms. http://techterms.com/definition/www. Retrieved 19 February 2010.
- ^ "The W3C Technology Stack". World Wide Web Consortium. http://www.w3.org/Consortium/technology. Retrieved 21 April 2009.
- ^ a b Hamilton, Naomi (31 July 2008). "The A-Z of Programming Languages: JavaScript". Computerworld. IDG. http://computerworld.com.au/article/255293/-z_programming_languages_javascript. Retrieved 12 May 2009.
- ^ Buntin, Seth (23 September 2008). "jQuery Polling plugin". http://buntin.org/2008/sep/23/jquery-polling-plugin/. Retrieved 2009-08-22.
- ^ Berners-Lee, Tim. "Frequently asked questions by the Press". W3C. http://w3.org/People/Berners-Lee/FAQ.html. Retrieved 27 July 2009.
- ^ Palazzi, P (2011) 'The Early Days of the WWW at CERN'
- ^ "automatically adding www.___.com". mozillaZine. 16 May 2003. http://forums.mozillazine.org/viewtopic.php?f=9&t=10980. Retrieved 27 May 2009.
- ^ Masnick, Mike (7 July 2008). "Microsoft Patents Adding 'www.' And '.com' To Text". Techdirt. http://techdirt.com/articles/20080626/0203581527.shtml. Retrieved 27 May 2009.
- ^ "MDBG Chinese-English dictionary – Translate". http://us.mdbg.net/chindict/chindict.php?page=translate&trst=0&trqs=World+Wide+Web&trlang=&wddmtm=0. Retrieved 27 July 2009.
- ^ "Frequently asked questions by the Press – Tim BL". W3.org. http://w3.org/People/Berners-Lee/FAQ.html. Retrieved 27 July 2009.
- ^ "It's not your grandfather's Internet". Strategic Finance. 2010. http://findarticles.com/p/articles/mi_hb6421/is_4_92/ai_n56479358/.
- ^ boyd, danah; Hargittai, Eszter (July 2010). "Facebook privacy settings: Who cares?". First Monday (University of Illinois at Chicago) 15 (8). http://www.uic.edu/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/3086/2589.
- ^ a b Ben-Itzhak, Yuval (18 April 2008). "Infosecurity 2008 – New defence strategy in battle against e-crime". ComputerWeekly (Reed Business Information). http://www.computerweekly.com/Articles/2008/04/18/230345/infosecurity-2008-new-defence-strategy-in-battle-against.htm. Retrieved 20 April 2008.
- ^ Christey, Steve and Martin, Robert A. (22 May 2007). "Vulnerability Type Distributions in CVE (version 1.1)". MITRE Corporation. http://cwe.mitre.org/documents/vuln-trends/index.html. Retrieved 7 June 2008.
- ^ (PDF) Symantec Internet Security Threat Report: Trends for July–December 2007 (Executive Summary). XIII. Symantec Corp.. April 2008. pp. 1–2. http://eval.symantec.com/mktginfo/enterprise/white_papers/b-whitepaper_exec_summary_internet_security_threat_report_xiii_04-2008.en-us.pdf. Retrieved 11 May 2008.
- ^ "Google searches web's dark side". BBC News. 11 May 2007. http://news.bbc.co.uk/2/hi/technology/6645895.stm. Retrieved 26 April 2008.
- ^ "Security Threat Report" (PDF). Sophos. Q1 2008. http://www.sophos.com/sophos/docs/eng/marketing_material/sophos-threat-report-Q108.pdf. Retrieved 24 April 2008.
- ^ "Security threat report" (PDF). Sophos. July 2008. http://www.sophos.com/sophos/docs/eng/papers/sophos-security-report-jul08-srna.pdf. Retrieved 24 August 2008.
- ^ Fogie, Seth, Jeremiah Grossman, Robert Hansen, and Anton Rager (2007) (PDF). Cross Site Scripting Attacks: XSS Exploits and Defense. Syngress, Elsevier Science & Technology. pp. 68–69, 127. ISBN 1-59749-154-3. Archived from the original on 25 June 2008. http://web.archive.org/web/20080625065121/http://www.syngress.com/book_catalog//SAMPLE_1597491543.pdf. Retrieved 6 June 2008.
- ^ O'Reilly, Tim (30 September 2005). "What Is Web 2.0". O'Reilly Media. pp. 4–5. http://www.oreillynet.com/pub/a/oreilly/tim/news/2005/09/30/what-is-web-20.html. Retrieved 4 June 2008. and AJAX web applications can introduce security vulnerabilities like "client-side security controls, increased attack surfaces, and new possibilities for Cross-Site Scripting (XSS)", in Ritchie, Paul (March 2007). "The security risks of AJAX/web 2.0 applications" (PDF). Infosecurity (Elsevier). Archived from the original on 25 June 2008. http://web.archive.org/web/20080625065122/http://www.infosecurity-magazine.com/research/Sep07_Ajax.pdf. Retrieved 6 June 2008. which cites Hayre, Jaswinder S. and Kelath, Jayasankar (22 June 2006). "Ajax Security Basics". SecurityFocus. http://www.securityfocus.com/infocus/1868. Retrieved 6 June 2008.
- ^ Berinato, Scott (1 January 2007). "Software Vulnerability Disclosure: The Chilling Effect". CSO (CXO Media): p. 7. Archived from the original on 18 April 2008. http://web.archive.org/web/20080418072230/http://www.csoonline.com/article/221113. Retrieved 7 June 2008.
- ^ Prince, Brian (9 April 2008). "McAfee Governance, Risk and Compliance Business Unit". eWEEK (Ziff Davis Enterprise Holdings). http://www.eweek.com/c/a/Security/McAfee-Governance-Risk-and-Compliance-Business-Unit/. Retrieved 25 April 2008.
- ^ Preston, Rob (12 April 2008). "Down To Business: It's Past Time To Elevate The Infosec Conversation". InformationWeek (United Business Media). http://www.informationweek.com/news/security/client/showArticle.jhtml?articleID=207100989. Retrieved 25 April 2008.
- ^ Claburn, Thomas (6 February 2007). "RSA's Coviello Predicts Security Consolidation". InformationWeek (United Business Media). http://www.informationweek.com/news/security/showArticle.jhtml?articleID=197003826. Retrieved 25 April 2008.
- ^ Duffy Marsan, Carolyn (9 April 2008). "How the iPhone is killing the 'Net". Network World (IDG). http://www.networkworld.com/news/2008/040908-zittrain.html. Retrieved 17 April 2008.
- ^ a b c "Web Accessibility Initiative (WAI)". World Wide Web Consortium. http://www.w3.org/WAI/l. Retrieved 7 April 2009.[dead link]
- ^ "Developing a Web Accessibility Business Case for Your Organization: Overview". World Wide Web Consortium. http://www.w3.org/WAI/bcase/Overview. Retrieved 7 April 2009.[dead link]
- ^ "Legal and Policy Factors in Developing a Web Accessibility Business Case for Your Organization". World Wide Web Consortium. http://www.w3.org/WAI/bcase/pol. Retrieved 7 April 2009.
- ^ "Web Content Accessibility Guidelines (WCAG) Overview". World Wide Web Consortium. http://www.w3.org/WAI/intro/wcag.php. Retrieved 7 April 2009.
- ^ "Internationalization (I18n) Activity". World Wide Web Consortium. http://www.w3.org/International/. Retrieved 10 April 2009.
- ^ Davis, Mark (5 April 2008). "Moving to Unicode 5.1". Google. http://googleblog.blogspot.com/2008/05/moving-to-unicode-51.html. Retrieved 10 April 2009.
- ^ "World Wide Web Consortium Supports the IETF URI Standard and IRI Proposed Standard" (Press release). World Wide Web Consortium. 26 January 2005. http://www.w3.org/2004/11/uri-iri-pressrelease.html. Retrieved 10 April 2009.
- ^ Lynn, Jonathan (19 October 2010). "Internet users to exceed 2 billion ...". Reuters. http://www.reuters.com/article/2010/10/19/us-telecoms-internet-idUSTRE69I24720101019. Retrieved 9 February 2011.
- ^ S. Lawrence, C.L. Giles, "Searching the World Wide Web," Science, 280(5360), 98–100, 1998.
- ^ S. Lawrence, C.L. Giles, "Accessibility of Information on the Web," Nature, 400, 107–109, 1999.
- ^ "The 'Deep' Web: Surfacing Hidden Value". Brightplanet.com. Archived from the original on 4 April 2008. http://web.archive.org/web/20080404044203/http://www.brightplanet.com/resources/details/deepweb.html. Retrieved 27 July 2009.
- ^ "Distribution of languages on the Internet". Netz-tipp.de. http://www.netz-tipp.de/languages.html. Retrieved 27 July 2009.
- ^ Alessio Signorini. "Indexable Web Size". Cs.uiowa.edu. http://www.cs.uiowa.edu/~asignori/web-size/. Retrieved 27 July 2009.
- ^ "The size of the World Wide Web". Worldwidewebsize.com. http://www.worldwidewebsize.com/. Retrieved 27 July 2009.
- ^ Alpert, Jesse; Hajaj, Nissan (25 July 2008). "We knew the web was big...". The Official Google Blog. http://googleblog.blogspot.com/2008/07/we-knew-web-was-big.html.
- ^ a b "Domain Counts & Internet Statistics". Name Intelligence. http://www.domaintools.com/internet-statistics/. Retrieved 17 May 2009.
- ^ "World Wide Wait". TechEncyclopedia. United Business Media. http://www.techweb.com/encyclopedia/defineterm.jhtml?term=world+wide+wait. Retrieved 10 April 2009.
- ^ Khare, Rohit and Jacobs, Ian (1999). "W3C Recommendations Reduce 'World Wide Wait'". World Wide Web Consortium. http://www.w3.org/Protocols/NL-PerfNote.html. Retrieved 10 April 2009.
- ^ Nielsen, Jakob (from Miller 1968; Card et al. 1991) (1994). "5". Usability Engineering: Response Times: The Three Important Limits. Morgan Kaufmann. http://www.useit.com/papers/responsetime.html. Retrieved 10 April 2009.
Further reading
- Niels Brügger, ed. Web History (2010) 362 pages; Historical perspective on the World Wide Web, including issues of culture, content, and preservation.
- Fielding, R.; Gettys, J.; Mogul, J.; Frystyk, H.; Masinter, L.; Leach, P.; Berners-Lee, T. (June 1999). Hypertext Transfer Protocol – HTTP/1.1. Request For Comments 2616. Information Sciences Institute. ftp://ftp.isi.edu/in-notes/rfc2616.txt.[dead link]
- Berners-Lee, Tim; Bray, Tim; Connolly, Dan; Cotton, Paul; Fielding, Roy; Jeckle, Mario; Lilley, Chris; Mendelsohn, Noah; Orchard, David; Walsh, Norman; Williams, Stuart (15 December 2004). Architecture of the World Wide Web, Volume One. Version 20041215. W3C. http://www.w3.org/TR/webarch/.
- Polo, Luciano (2003). "World Wide Web Technology Architecture: A Conceptual Analysis". New Devices. http://newdevices.com/publicaciones/www/. Retrieved 31 July 2005.
- Skau, H.O. (March 1990). "The World Wide Web and Health Information". New Devices. http://newdevices.com/publicaciones/www/. Retrieved 1989.
External links
- Early archive of the first Web site
- Internet Statistics: Growth and Usage of the Web and the Internet
- Living Internet A comprehensive history of the Internet, including the World Wide Web.
- Web Design and Development at the Open Directory Project
- World Wide Web Consortium (W3C)
- W3C Recommendations Reduce "World Wide Wait"
- World Wide Web Size Daily estimated size of the World Wide Web.
- Antonio A. Casilli, Some Elements for a Sociology of Online Interactions
- The Erdős Webgraph Server offers weekly updated graph representation of a constantly increasing fraction of the WWW.
|
Coordinates: 46°13′57″N 6°02′42″E / 46.2325°N 6.045°E