World Wide Web. Before WWW

Size: px

Start display at page:

Download "World Wide Web. Before WWW"

Gladys Perkins
6 years ago
Views:

1 FEUP, João Neves World Wide Web CAcer t WoT User Digitally signed by CAcert WoT User DN: cn=cacert WoT User, =joao.neves@i nescporto.pt, =b2d718a54c3 83ce1a9d48aa87e2ef 687ee8769f0 Date: :50:40 Z Before WWW Major search tools: Gopher and Archie Query FTP archives and Usenet is the main goal Archie Search FTP archives indexes Filename based queries Gopher RFC1436: The Internet Gopher Protocol (a distributed document search and retrieval protocol) Friendly interface Menu driven queries João Neves 2 1

2 Web Born Tim Berners-Lee et al. at CERN in 1991 HyperText Transfer Protocol (HTTP) Hypertext - embedded links in text to link to another text document Hyperlinks RFC1945, May 1996, HTTP/1.0 RFC2068 obsolete by RFC2616, June 1999, HTTP/1.1 João Neves 3 Internet Evolution Year Hosts(*) João Neves 4 2

Total Sites Across All Domains August 1995 - March 2008 Source http://news.netcraft.

html João Neves 5 Layering HyperText Transfer Protocol Telnet Simple Network Management

3 Total Sites Across All Domains August March 2008 Source João Neves 5 Layering HyperText Transfer Protocol Telnet Simple Network Management Dynamic Host Configuration Transmission Control Protocol (TCP) User Datagram Protocol (UDP) Internet Protocol (IP) Ethernet Wi-Fi SONET João Neves 6 3

HTTP Standard protocol for web transfer Request-response interaction between client and server The server has resources as HTML files and images Request methods: GET, HEAD, PUT, POST, DELETE,

4 HTTP Standard protocol for web transfer Request-response interaction between client and server The server has resources as HTML files and images Request methods: GET, HEAD, PUT, POST, DELETE, Response: Status line + additional info (e.g., a web page) João Neves 7 Introduction to HTTP It has been in use by the World-Wide Web global information initiative since 1990 Its first version (referred to as HTTP/0.9) was a simple protocol for raw data transfer across the Internet HTTP/1.0 improved the protocol by allowing messages to be in the format of MIME-like messages: containing metainformation about the data transferred and modifiers on the request/response semantics João Neves 8 4

5 HTTP Transaction Client HTTP Server HTTP client: web browser WebRoot HTTP server: web server Standard port: 80 dir Suggested alternate ports: 81, 8080, 8081 HTTP is used to transmit resources file.html File/documents Image files Query results Outputs from CGI (Common Gateway Interface) scripts Anything that can be identified by a URL João Neves 9 Web Clients Lynx 2.0 (1993, character based interface) NCSA Mosaic (1993, first with graphical interface) Marc Andreessen (author of Mosaic) moved to Netscape Microsoft Internet Explorer ( new name for Mosaic ) Mozilla Firefox Opera Safari Chrome João Neves 10 5

6 The Browser The browser 1. Fetches the page requested; 2. Interprets the text and formatting commands that it contains; 3. Displays the page properly formatted on the screen. On the page strings of text that are links to other pages, called hyperlinks On the screen the hyperlinks are highlighted, either by underlining, displaying them in a special color, or both João Neves 11 Web Servers NCSA HTTPd non-commercial free Apache HTTP Server freeware Apache Tomcat freeware lighttpd freeware Microsoft Internet Information Services (IIS) payware Zeus Web Server payware Zope freeware... João Neves 12 6

Server Share Server Share amongst the Million Busiest Sites, March 2009 source http://news.netcraft.

7 Server Share Server Share amongst the Million Busiest Sites, March 2009 source João Neves 13 HTML SHTML SGML XML Markup Languages João Neves 14 7

8 Markup Markup are codes inserted into texts documents to manage formatting, printing or other process. A description markup indicates the nature, function, or content of the data in a file. A procedural markup defines what processing is to be carried out at particular points in the document. João Neves 15 HyperText Markup Language Language in which web pages are written Contains formatting commands Tells browser what to display and how to display Examples: <TITLE> Welcome to My Great Site </TITLE> The title of this page is Welcome to My Great Site <B>Great News!</B> Set Great News! in boldface <A HREF= >I m the One</A> A link pointing to the web page with the text I m the One displayed João Neves 16 8

9 Sample HTML Tags <A> </A> Anchor link or name <BODY> </BODY> Document Contents <BR> Break <FORM> </FORM> Input form <H1> </H1> Heading level 1 <HEAD> </HEAD> Header of a document <HR> Horizontal Rule <HTML> </HTML> The doc type is HTML <LI> List Item <OL> </OL> Ordered List <P> </P> Paragraph break <PRE> </PRE> Preformatted text <TITLE> </TITLE> Document title <UL> Unnumbered list João Neves 17 Uniform Resource Identifiers A URI is an identifier for some resource, and a Uniform Resource Locator (URL) gives you specific information as to obtain that resource HTTP is also used as a generic protocol for communication between user agents and proxies/gateways to other Internet systems, including those supported by the next protocols: SMTP, NNTP, FTP RFC 2396, August 1998 In this way, HTTP allows basic hypermedia access to resources available from diverse applications João Neves 18 9

10 Uniform Resource Identifiers The following examples illustrate URL that are in common use: Name Utility Example ftp ftp scheme for File Transfer Protocol services ftp://ftp.is.co.za/rfc/rfc1808.txt http http scheme for Hypertext Transfer Protocol services file Local file file:/usr/local/etc/ntp.conf news news scheme for USENET news groups and articles news:comp.infosystems. telnet telnet scheme for interactive services via the TELNET telnet://melvyl.ucop.edu/ Protocol mailto mailto scheme for electronic mail addresses gopher gopher scheme for Gopher and Gopher+ Protocol services gopher://stap.umn.edu/00/weather/ca/los%20angeles João Neves 19 Uniform Resource Locator <scheme>: // hostname [: port] / path [; parameters] [?query] Some URL schemes use the format "user:password" in the userinfo field. This practice is NOT RECOMMENDED, because the passing of authentication information in clear text (such as URI) has proven to be a security risk in almost every case where it has been used. [RFC2396] João Neves 20 10

11 HTTP HyperText Transfer Protocol A very simple, stateless protocol for sessionless exchanges Browser creates a new connection each time it wants to make a new request (for a page, image, etc.) Exceptions: HTTP 1.1 added support for persistent connections and pipelining Clients + servers might keep state information Cookies provide a way of recording state João Neves 21 The http protocol: more http: TCP transport service client initiates TCP connection (creates socket) to server, port 80 server accepts TCP connection from client http messages (application-layer protocol messages) exchanged between browser (http client) and Web server (http server) TCP connection closed http is stateless server maintains no information about past client requests João Neves 22 11

12 HTTP GET /path/to/file/index.html HTTP/1.0 HTTP method Path: the part of the URL after the hostname, i.e. request URI The HTTP version João Neves 23 HTTP Session telnet 80 [...] GET /~jneves/index.html HTTP/1.0 From: User-Agent: Camachina/5.0 HTTP/ OK Date: Tue, 26 May :06:13 GMT Server: Apache/2.30 (Unix) PHP/5.5 DAV/2 mod_perl/2.9 Perl/v5.20 Last-Modified: Fri, 04 May :41:20 GMT Accept-Ranges: bytes Content-Length: 91 Connection: close Content-Type: text/html <html> <head> <meta HTTP-EQUIV="REFRESH" content="0; url=./index.shtml"> </head> </html> Connection closed by foreign host. João Neves 24 12

13 HTTP Request Headers Header From User-Agent Accept Accept-encoding Accept-Language Referrer If-Modified-Since Content-length Content-Type Pragma: no-cache Description RFC822 address of the user Client Software File types that client will accept, e.g., text/plain, text/html Compression methods, e.g., x-compress; x-zip Language(s) used (optional) URL of the document (or element within the document) from which the URL in the request was obtained Return document if modified since specified date Length in octets of data to follow Type of the item Directive understood by a proxy server; When present the proxy should not return a document from the cache João Neves 25 HTTP Response Headers Header Server Date Last-Modified Expires Location Pragma MIME-version Link Content-Length Allowed Description Server Software Current Date Modification date of the document Document expiration date The location of the document in redirection responses A hint, e.g. no cache URL of document s parent Length in octets Requests that user can issue, e.g., GET João Neves 26 13

14 HTTP Status Codes Code Text 2xx Success 3xx Redirection 301 Moved 302 Found 4xx Client Errors 400 Bad Request 401 Unauthorized 404 Not found 5xx Server Errors 500 Internal Error 502 Service Overload João Neves 27 HTTP over TLS bash-4.0# openssl s_client -connect secure.xptoo.org:443 -showcerts CONNECTED( ) [ ] --- GET / HTTP/1.0 HTTP/ OK [ ] João Neves 28 14

15 HTTP 1.1 Features Persistent TCP Connections: remain open for multiple requests Partial Document Transfers: clients can specify start and stop positions Conditional Fetch: several additional conditions Better content negotiation More flexible authentication João Neves 29 Static vs. Dynamic Pages HTML pages vs. database Personalized Context-aware services Browsing Device-dependent João Neves 30 15

16 HTTP Proxy Why needed How it works Different types Advantages vs. disadvantages João Neves 31 Why Web Caching (Proxies)? origin servers Assume: cache is close to client (e.g., in same network) smaller response time: cache closer to client decrease traffic to distant servers link out of institutional/local ISP network often bottleneck institutional network Internet 1,5 Mb/s access link (bottleneck ) 100 Mb/s LAN institutional cache João Neves 32 16

17 HTTP Proxy An intermediary program which acts as both a server and a client for the purpose of making requests on behalf of other clients; A proxy must implement both the client and server requirements of this specification; The client makes a request to the proxy server using the complete URL; The proxy server connects to the remote server and requests the resource relative to that server (no protocol and hostname in the URL); Requests are serviced internally or by passing them on, with possible translation, to other servers. João Neves 33 HTTP Proxy GET HTTP/1.0 Client HTTP/ Document... HTTP Proxy Server GET /path/to/file.html HTTP/1.0 HTTP/ Document... Server WebRoot The client makes a request to the proxy server using the complete URL; The proxy server connects to the remote server and requests the resource relative to that server (no protocol and hostname in the URL). dir file.html João Neves 34 17

18 HTTP Proxy + Cache GET HTTP/1.0 Client HTTP/ Document... HTTP Proxy Server GET /path/to/file.html HTTP/1.0 HTTP/ Document... Server WebRoot dir Cache file.html João Neves 35 Different Types Transparent Configured ( Automatic, discovered by the browser (WPAD - Web Proxy AutoDiscovery) João Neves 36 18

19 Advantages vs. Disadvantages Advantages Traffic reduction Traffic management Security Disavantages First access delay Old pages on cache João Neves 37 Web Load Handling Thousands of clients Load sharing DNS Round Robin Web Switching L4 L7 Load Balancing Devices Radware Alteon (ex-nortel) A10 Networks Cisco Content Switching... Akamai João Neves 38 19

(2006) ISBN 0-13-187671-6 Tanenbaum, Andrew S.

20 Bibliography Comer, Douglas E. Internetworking with TCP/IP (VOL I) Prentice Hall, 5th Ed. (2006) ISBN Tanenbaum, Andrew S. Computer Networks Prentice Hall International Editions 4th Ed. (2003) ISBN João Neves 39 20

WEB TECHNOLOGIES CHAPTER 1

WEB TECHNOLOGIES CHAPTER 1 WEB ESSENTIALS: CLIENTS, SERVERS, AND COMMUNICATION Modified by Ahmed Sallam Based on original slides by Jeffrey C. Jackson THE INTERNET Technical origin: ARPANET (late 1960