1 / 17
Télécharger la présentation

Web Hosting Fundamentals: Platforms, Security, and Performance

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. Chapter 22 Web Hosting and Internet Servers Xuanxuan Su

  2. Topics • Web • FTP • News

  3. Web Hosting • Web hosting platform • Reliability • Maintainability • Security • Performance • Unix vs. Windows

  4. HTTP protocol • The foundation of the WWW • TCP-based protocol • Transmit documents • Text • Pictures/Animation • Audio/Video • Client(web browsers) initiated • Platform independence

  5. Web Server • Answer HTTP requests • Listens on TCP port 80 • Support Services • Secure HTTP • Secure Socket Layer protocol • Listens on TCP port 443 • FTP

  6. URL • Protocol or application • Hostname • TCP/IP port • Directory • Filename

  7. URL Examples • https://my.umbc.edu/fcgi-bin/myumbc.fcgi • http://sunserver1.cs.umbc.edu:8080/ • telnet://spot.acme.com

  8. CGI Scripting • What’s CGI? • Common Gateway Interface • Dynamically generate content • Usually Perl/C programs • Security Concern • CGI scripts have access to files, network connections, and other methods of moving data • Anyone can run a program on HTTP server

  9. HTTP Server Installation • Why Apache HTTP server? • A powerful, flexible, HTTP/1.1 compliant web server • Support OS: Unix, Linux, Windows NT/9x, Netware 5.x, OS/2, and etc. • Open source • Highly configurable and extensible with third-party modules

  10. Configuring Apache • Configuration files in the conf directory • httpd.conf • TCP port • Location of log files and document files • Network and performance parameters • Virtual hosts • srm.conf • Controls server access resources • DocumentRoot Definition • access.conf • Controls access on a per-file or per-directory basis

  11. Running Apache • Httpd daemon • Start by hand • Start from rc scripts

  12. Virtual Interfaces • Why virtual interfaces? • Host multiple websites on a single server • Configuring • Create the virtual interface at the TCP/IP level • Interface:instance, for example, eth0:1 • Use ifconfig command • /etc/sysconfig/network-scripts make it permanent • Tell Apache about a virtual interface • Add VirtualHost clauses in the http.conf file

  13. Caching and Proxy Servers • Why proxy? • Exponentially growing information on Internet • Use replication on a national, regional or site level • Squid Internet Object Cache • http://www.squid-cache.org/ • Support HTTP FTP, gopher, and SSL • reduce access time as well as bandwidth consumption

  14. Setting up Squid • Most important resource is physical memory, RAM and disk space • Compile • % tar xzf squid-2.0.RELEASE-src.tar.gz • % cd squid-2.0.RELEASE • % ./configure • % make • Install • % make install • edit and customize the squid.conf file

  15. Setting up Squid(cont) • Start • create the swap directories % /usr/local/squid/bin/squid –z • Start Squid by command % /usr/local/squid/bin/squid (Squid 2.X) % /usr/local/squid/bin/RunCache (Squid 1.1.X)

  16. Anonymous FTP Server Setup • Why FTP? • Distributes software, document drafts and the like • Allows users to inspect the properties of files • Anonymous FTP • FTP daemon: ftpd • Managed by inetd • /etc/inetd.cof • /etc/services • Installed and turned on by default in Red Hat

  17. Usernet News • What’s usenet? • the set of machines that exchange articles tagged with one or more universally-recognized labels, called newsgroups • Delivery method: flood fill • Usenet news feeds • Retain the services of a company that specializes in hosting Usenet • Get a “pull” feed from upstream service provider • Receive a normal feed that includes the article headers but not the bodies. The article is pulled only when a user asks to.

More Related