Planning, configuring, running and maintaining a web server -1

setting up a web server brief review of how a web server works planning required before setup server files and directories Apache configuration

how a web server works information on web identified using a URL UNIFORM RESOURCE LOCATOR browser requests information from the server (defined by URL) using HTTP HYPER TEXT TRANSFER PROTOCOL server returns information to browser (using HTTP) in HTML format HYPER TEXT MARKUP LANGUAGE

browser server HTML HTTP URL

planning required server platform (what hardware and operating system should be used) web server and associated software provision of sufficient expertise and other resources for chosen system clear responsibilities policies for updating information, acceptable use, etc. more?

planning—platform easy to install open standards, lots of online support runs on any PC architecture—wide range of peripheral hardware drivers available inexpensive, fast other criteria?

planning—web software Apache is world leader, has evolved from one of first web server programs (NCSA) open standards, lots of online support team of experts developing updates runs on many computer platforms (at home with Unix) inexpensive, fast modular approach for loading new capabilities other criteria?

files—Apache httpd, the server program httpd.conf, main configuration file access_log, log of all accesses error_log, log of all errors httpd.pid, contains process id of running server program

directories—Apache conf, for configuration files logs, for logs html, for web pages cgi-bin, for programs

files—Apache configuration how httpd runs set ‘port’ for network access identify log files and other configuration files

Apache—checking look at site with browser remotely check httpd active processes on server ps -ef | grep httpd checking problems, confirming restart tail error_log telnet to your_port on server and issue GET request followed by blank line telnet 80 GET / HTTP/1.0