1 / 32

Internet Engineering

Internet Engineering. Web Servers. Introduction. Company needs to provide various web services Hosting intranet applications Company web site Various internet applications Therefore there is a need to provide http server First we have a look at what http protocol is

inigo
Télécharger la présentation

Internet Engineering

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Internet Engineering Web Servers

  2. Introduction • Company needs to provide various web services • Hosting intranet applications • Company web site • Various internet applications • Therefore there is a need to provide http server • First we have a look at what http protocol is • Then we talk about Apache web server as leading web server application

  3. The World Wide Web (WWW) • Global hypertext system • Initially developed in 1989 • By Tim Berners Lee at the European Laboratory for Particle Physics, CERN in Switzerland. • To facilitate an easy way of sharing and editing research documents among a geographically dispersed groups of scientists. • In 1993, started to grow rapidly • Mainly due to the NCSA developing a Web browser called Mosaic (an X Window-based application) • First graphical interface to the Web  More convenient browsing • Flexible way people can navigate through worldwide resources in the Internet and retrieve them

  4. Web Browsers • Provides access to a Web server • Basic components • HTML interpreter • HTTP client used to retrieve HTML pages • Some also support • FTP, NTTP, POP, SMTP, …

  5. Web Servers • Definitions • A computer, responsible for accepting HTTP requests from clients, and serving them Web pages. • A computer program that provides the above mentioned functionality. • Common features • Accepting HTTP requests from the network • Providing HTTP response to the requester • Typically consists of an HTML • Usually capable of logging • Client requests/Server responses

  6. Web Servers cont. • Returned content • Static • Comes from an existing file • Dynamic • Dynamically generated by some other program/script called by the Web server. • Path translation • Translate the path component of a URL into a local file system resource • Path specified by the client is relative to the server’s root dir

  7. http protocol • Created to define the communication between a web server and a client • It's the network protocol used to deliver virtually all files and other data (collectively called resources) on the World Wide Web • A browser is an HTTP client because it sends requests to an HTTP server (Web server), which then sends responses back to the client. • The standard (and default) port for HTTP servers to listen on is 80, though they can use any port.

  8. Structure of http transactions • Like most network protocols, HTTP uses the client-server model: An HTTP client opens a connection and sends a request message to an HTTP server; the server then returns a response message, usually containing the resource that was requested • Format of a http message: <initial line, different for request vs. response> Header1: value1 Header2: value2 Header3: value3 <optional message body goes here, like file contents or query data; it can be many lines long, or even binary data >

  9. Initial line • A typical initial request line: • GET /path/to/file/index.html HTTP/1.0 • Initial response line: • HTTP/1.0 200 OK • HTTP/1.0 404 Not Found • Status code: • 1xx indicates an informational message only • 2xx indicates success of some kind • 3xx redirects the client to another URL • 4xx indicates an error on the client's part • 5xx indicates an error on the server's part • Common status codes: • 200 OK • 404 Not Found • 301 Moved Permanently • 302 Moved Temporarily • 303 See Other(HTTP 1.1 only) • 500 Server Error

  10. Header lines • Typical request headers: • From: email address of requester • User-Agent: for example User-agent: Mozilla/3.0Gold • Typical response headers: • Server: for example Server: Apache/1.2b3-dev • Last-modified: fro example Last-Modified: , 19 Feb 2006 23:59:59 GMT

  11. Message body • In a response, this is where the requested resource is returned to the client (the most common use of the message body), or perhaps explanatory text if there's an error. • In a request, this is where user-entered data or uploaded files are sent to the server. • If an HTTP message includes a body, there are usually header lines in the message that describe the body. In particular, • The Content-Type: header gives the MIME-type of the data in the body, such as text/html or image/gif. • The Content-Length: header gives the number of bytes in the body.

  12. Sample HTTP exchange • To retrieve the file at the URL http://www.somehost.com/path/file.html • Request: GET /path/file.html HTTP/1.0 From: someuser@jmarshall.com User-Agent: HTTPTool/1.0 [blank line here] • Response: HTTP/1.0 200 OK Date: Fri, 31 Dec 1999 23:59:59 GMT Content-Type: text/html Content-Length: 1354 <html> <body> <h1>Happy New Millennium!</h1> (more file contents) . . . </body> </html>

  13. HTTP methods • GET: request a resource by url • HEAD • is just like a GET request, except it asks the server to return the response headers only, and not the actual resource (i.e. no message body). • This is useful to check characteristics of a resource without actually downloading it, thus saving bandwidth. • POST • A POST request is used to send data to the server to be processed in some way, like by a CGI script. • There's a block of data sent with the request, in the message body. There are usually extra headers to describe this message body, like Content-Type: and Content-Length:. • The request URI is not a resource to retrieve; it's usually a program to handle the data you're sending. • The HTTP response is normally program output, not a static file.

  14. HTTP 1.1 • It is a superset of HTTP 1.0. Improvements include: • Faster response, by allowing multiple transactions to take place over a single persistent connection. • Faster response and great bandwidth savings, by adding cache support. • Faster response for dynamically-generated pages, by supporting chunked encoding, which allows a response to be sent before its total length is known. • Efficient use of IP addresses, by allowing multiple domains to be served from a single IP address.

  15. HTTP 1.1 clients • To comply with HTTP 1.1, clients must • Include Host: header with each request : GET /path/file.html HTTP/1.1 Host: www.host1.com:80 [blank line here] • Accept response with chunked data: HTTP/1.1 200 OK Date: Fri, 31 Dec 1999 23:59:59 GMT Content-Type: text/plain Transfer-Encoding: chunked 1a; ignore-stuff-here abcdefghijklmnopqrstuvwxyz 10 1234567890abcdef 0 some-footer: some-value another-footer: another-value [blank line here]

  16. HTTP 1.1 clients (cont.) • Either support persistent connections or include the “Connection: close” header with each request • Handle the “100 continue” response HTTP/1.1 100 Continue HTTP/1.1 200 OK Date: Fri, 31 Dec 1999 23:59:59 GMT Content-Type: text/plain Content-Length: 42 some-footer: some-value another-footer: another-value abcdefghijklmnoprstuvwxyz1234567890abcdef

  17. HTTP 1.1 servers • To comply with HTTP 1.1, servers must: • Requiring the Host: Header. Without it server must response with something like below: HTTP/1.1 400 Bad Request Content-Type: text/html Content-Length: 111 <html><body> <h2>No Host: header received</h2> HTTP 1.1 requests must include the Host: header. </body></html> • Accepting absolute URL’s • GET http://www.somehost.com/path/file.html HTTP/1.2 • Chunked transfer

  18. HTTP 1.1 servers (cont.) • Persistent Connections and the "Connection: close" Header • Using the "100 Continue" Response • The Date: Header for caching • Handling Requests with If-Modified-Since: or If-Unmodified-Since: Headers HTTP/1.1 304 Not Modified Date: Fri, 31 Dec 1999 23:59:59 GMT [blank line here] • Supporting the GET and HEAD methods • Supporting HTTP 1.0 Requests

  19. First Web Server • Berners-Lee wrote two programs • A browser called WorldWideWeb • The world’s first Web server, which ran on NeXSTEP • The machine is on exhibition at CERN’s public museum

  20. Most Famous Web Servers • Apache HTTP Server from Apache Software Foundation • Internet Information Services (IIS) from Microsoft • Sun Java Web Server from Sun Microsystems • Formerly Sun ONE Web Server, iPlanet Web Server, and Netscape Enterprise Server • Zeus Web Server from Zeus Technology

  21. Web Servers Usage – Statistics • The most popular Web servers, used for public Web sites, are tracked by Netcraft Web Server Survey • Details given by Netcraft Web Server Reports • Apache is the most popular since April 1996 • Currently (February 2006) about • 66.64%  Apache • 25.11%  Microsoft (IIS, PWS, etc.) • 0.73%  Zeus • 0.67%  Sun (Java Web Server, Netscape Enterprise, iPlanet, …)

  22. Web Servers Usage – Statistics cont. Total Sites August 1995 - February 2006 Market Share for Top Servers August 1995 - February 2006 Totals for Active Servers June 2000 - February 2006

  23. Apache web server features and functions • Caching • Content negotiation • A resource may be available in several different representations. • For example, it might be available in different languages or different media types, or a combination. • One way of selecting the most appropriate choice is to give the user an index page, and let them select. • However it is often possible for the server to choose automatically by the help of request headers: Accept-Language: fr; q=1.0, en; q=0.5Accept: text/html; q=1.0, text/*; q=0.8, image/gif; q=0.6, image/jpeg; q=0.6, image/*; q=0.5, */*; q=0.1

  24. Apache web server features and functions (cont.) • DSO (Dynamic Shared Object) mechanism • Log files • In order to effectively manage a web server, it is necessary to get feedback about the activity and performance of the server as well as any problems that may be occurring • Error log: • [Wed Oct 11 14:32:52 2000] [error] [client 127.0.0.1] client denied by server configuration: /export/home/live/ap/htdocs/test • Access log: • Common log format: • 127.0.0.1 - frank [10/Oct/2000:13:55:36 -0700] "GET /apache_pb.gif HTTP/1.0" 200 2326 • Combined log format: • 127.0.0.1 - frank [10/Oct/2000:13:55:36 -0700] "GET /apache_pb.gif HTTP/1.0" 200 2326 "http://www.example.com/start.html" "Mozilla/4.08 [en] (Win98; I ;Nav)"

  25. Apache web server features and functions (cont.) • Mapping URLs to file system locations: • DocumentRoot • Alias directive: • Alias /docs /var/web • the URL http://www.example.com/docs/dir/file.html will be served from /var/web/dir/file.html. • AliasMatch: • ScriptAliasMatch ^/~([a-zA-Z0-9]+)/cgi-bin/(.+) /home/$1/cgi-bin/$2 • will map a request to http://example.com/~user/cgi-bin/script.cgi to the path /home/user/cgi-bin/script.cgi and will treat the resulting file as a CGI script • User Directories: • http://www.example.com/~user/file.html

  26. Apache web server features and functions (cont.) • Mapping URLs to file system locations: • URL redirection: • Redirect permanent /foo/ http://www.example.com/bar/ • Reverse proxy: • Apache also allows you to bring remote documents into the URL space of the local server. • This technique is called reverse proxying because the web server acts like a proxy server by fetching the documents from a remote server and returning them to the client. • ProxyPass /foo/ http://internal.example.com/bar/ • Mod_speling for file not found errors

  27. Apache web server features and functions (cont.) • Access control to filesystem • <Directory /> Order Deny,Allow Deny from all </Directory> • Directory /usr/users/*/public_html> Order Deny,Allow Allow from all </Directory>

  28. Apache web server features and functions (cont.) • SSI (Server Side Includes) • SSI (Server Side Includes) are directives that are placed in HTML pages, and evaluated on the server while the pages are being served. • They let you add dynamically generated content to an existing HTML page, without having to serve the entire page via a CGI program, or other dynamic technology. • <!--#config timefmt="%A %B %d, %Y" -->Today is <!--#echo var="DATE_LOCAL" --> • <!--#include virtual="/footer.html" --> • <!--#include virtual="/cgi-bin/counter.pl" -->

  29. Apache web server features and functions (cont.) • Virtual hosting • The term Virtual Host refers to the practice of running more than one web site (such as www.company1.com and www.company2.com) on a single machine. • Virtual hosts can be "IP-based", meaning that you have a different IP address for every web site • or "name-based", meaning that you have multiple names running on each IP address. The fact that they are running on the same physical server is not apparent to the end user.

  30. Apache web server features and functions (cont.) • IP based Virtual hosting • the server must have a different IP address for each IP-based virtual host. • This can be achieved by the machine having several physical network connections • <VirtualHost www.smallco.com>ServerAdmin webmaster@mail.smallco.comDocumentRoot /groups/smallco/wwwServerName www.smallco.comErrorLog /groups/smallco/logs/error_logTransferLog /groups/smallco/logs/access_log</VirtualHost><VirtualHost www.baygroup.org>ServerAdmin webmaster@mail.baygroup.orgDocumentRoot /groups/baygroup/wwwServerName www.baygroup.orgErrorLog /groups/baygroup/logs/error_logTransferLog /groups/baygroup/logs/access_log</VirtualHost>

  31. Apache web server features and functions (cont.) • Name based Virtual hosting • HTTP 1.1 compliant clients needed; i.e. Host header should be included in request • NameVirtualHost *:80<VirtualHost *:80>ServerName www.domain.tldServerAlias domain.tld *.domain.tldDocumentRoot /www/domain</VirtualHost><VirtualHost *:80>ServerName www.otherdomain.tldDocumentRoot /www/otherdomain</VirtualHost>

  32. References • http://www.jmarshall.com/easy/http/ • TCP/IP Tutorial and Technical Overview, Rodriguez, Gatrell, Karas, Peschke, IBM redbooks, August 2001 • Wikipedia, the free encyclopedia • Apache: The Definitive Guide, 2nd edition, Ben Laurie, Peter Laurie, O’Reilly, February 1999 • Webmaster in a nutshell, 1st edition, Stephen Spainhour, Valerie Quercia, O’Reilly, October 1996 • Netcraft: February 2006 Web Server Survey

More Related