DOCSLIB.ORG

Apache Configuration Due Date: Nov 8 Points: 25 Points

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Apache Configuration Due Date: Nov 8 Points: 25 Points Apache Configuration Due Date: Nov 8 Points: 25 Points Objective: To gain experience with configuring the Apache web server Equipment Needed The Ubuntu system that you have already downloaded has the apache daemon along with html files that are needed in this experience. You will also need an Ethernet connection, i.e. a cat 5 cable. Background The Apache HTTP Server, commonly referred to as Apache is a web server notable for playing a key role in the initial growth of the World Wide Web. In 2009 it became the first web server to surpass the 100 million web site milestone. The majority of web servers using Apache run the Linux operating system. Apache is developed and maintained by an open community of developers under the auspices of the Apache Software Foundation. The application is available for a wide variety of operating systems, including Unix, GNU, FreeBSD, Linux, Solaris, Novell NetWare, Mac OS X, Microsoft Windows, OS/2, TPF, and eComStation. Released under the Apache License, Apache is characterized as open source software. Since April 1996 Apache has been the most popular HTTP server on the World Wide Web. As of September 2009, Apache served over 54.48% of all websites and over 66% of the million busiest. The first version of the Apache web server was created by Robert McCool, who was heavily involved with the National Center for Supercomputing Applications web server, known simply as NCSA HTTPd. When McCool left NCSA in mid-1994, the development of httpd stalled, leaving a variety of patches for improvements circulating through e-mails. These patches were provided by a number of other developers besides McCool: Brian Behlendorf, Roy Fielding, Rob Hartill, David Robinson, Cliff Skolnick, Randy Terbush, Robert S. Thau, Andrew Wilson, Eric Hagberg, Frank Peters and Nicolas Pioch, and they thus helped to form the original "Apache Group". Version 2 of the Apache server was a substantial re-write of much of the Apache 1.x code, with a strong focus on further modularization and the development of a portability layer, the Apache Portable Runtime. The Apache 2.x core has several major enhancements over Apache 1.x. These include UNIX threading, better support for non-Unix platforms (such as Microsoft Windows), a new Apache API, and IPv6 support. The first alpha release of Apache 2 was in March 2000, with the first general availability release on April 6, 2002. Version 2.2 introduced a more flexible authorization API. It also features improved cache modules and proxy modules. See http://en.wikipedia.org/wiki/Apache_server for more information. Procedure 1. Basic Configuration Apache is configured by placing directives in plain text configuration files. The main configuration file is called apache2.conf. In addition, other configuration files may be added using the Include directive, and wildcards can be used to include many configuration files. Any directive may be placed in any of these configuration files. Changes to the main configuration files are only recognized by Apache2 when it is started or restarted. The default Apache2 configuration file is /etc/apache2/apache2.conf . We will be editing this file to configure the Apache2 server. Through modification of apache2.conf one can configure the port number, document root, modules, log files, virtual hosts, etc. The first action to take is to save an original copy of any configuration file. Hence, you will want to $ sudo cp apache2.conf apache2.conf.orig 2. Configuring User Authentication & Access Control and Logging (basic) If you have information on your web site that is sensitive or intended for only a small group of people, these steps will ensure that the people that see those pages are the people that you wanted to see them. You'll need to create a password file. This file should be placed somewhere not accessible from the web (we will violate this rule for this experience). This is so that folks cannot download the password file. To create the password file, type: $ cd /var/www/ $ sudo htpasswd -c /var/www/passwords <your_username> Next, you'll need to configure the server to request a password and tell the server which users are allowed access. You can do this either by editing the httpd.conf file or using an .htaccess file; for this experience we will be using the .htaccess file. If you use the vim editor, in the /var/www/ directory type $ sudo vim .htaccess Type in the following information and save the file: AuthType Basic AuthName "Restricted Files" AuthUserFile /var/www/passwords Require user <your_username> Let's examine each of those directives individually. The AuthType directive selects the method that is used to authenticate the user. The most common method is Basic, and this is the method implemented by mod_auth. It is important to be aware, however, that Basic authentication sends the password from the client to the browser unencrypted. This method should therefore not be used for highly sensitive data. Apache supports one other authentication method: AuthType Digest. This method is implemented by mod_auth_digest and is much more secure. Only the most recent versions of clients are known to support Digest authentication. The AuthName directive sets the Realm to be used in the authentication. The realm serves two major functions. First, the client often presents this information to the user as part of the password dialog box. Second, it is used by the client to determine what password to send for a given authenticated area. The AuthUserFile directive sets the path to the password file that we just created with htpasswd. If you have a large number of users, it can be quite slow to search through a plain text file to authenticate the user on each request. Apache also has the ability to store user information in fast database files. The mod_auth_dbm module provides the AuthDBMUserFile directive. These files can be created and manipulated with the dbmmanage program. Finally, the Require directive provides the authorization part of the process by setting the user that is allowed to access this region of the server. In the next section, we discuss various ways to use the Require directive. For more information visit http://httpd.apache.org/docs/2.0/howto/auth.html Next, open the virtual hosts file: $ sudo vim /etc/apache2/sites-available/default Find the section that looks similar to below: <Directory /var/www/> ... AllowOverride None ... </Directory> Modify the ‘AllowOverride None’ to ‘AllowOverride All’ and save the file. Next move the ‘passwordProtected.html’ file from the ‘Apache’ directory on your desktop to /var/www/. Lastly, restart apache with: $ sudo /etc/init.d/apache2 restart Open a web browser and enter ‘http://localhost/passwordProtected.html’. You should be prompted for a username/password Enter an INCORRECT password, followed by the correct password. After entering the correct password, you should be allowed access to the webpage Now let’s take a look at the log-file $ sudo vim /var/log/apache2/error.log $ sudo vim /var/log/apache2/access.log What is/was being recorded in each log file? *Do a Print-Screen showing the pertinent sections of each log-file for Reporting* 3. Configuring Per-user Web Directories (intermediate) On systems with multiple users, each user can be permitted to have a web site in their home directory using the UserDir directive. Visitors to a URL http://example.com/~username/ will get content out of the home directory of the user "username", out of the subdirectory specified by the UserDir directive; this is very similar to how department and university web-hosting is handled for employees and students. Remember that we have the user “student” from the Authentication experience. Next we will create a ‘public_html’ directory under student by $ sudo mkdir /home/student/public_html When running a web-server Apache runs as the ‘www-data’ user under the group ‘www-data’ because of this we must give the “www-data” group privileges to read content of the newly added user. If this step is omitted, when accessing the web-page, you will get a ‘Forbidden Error’. $ sudo chgrp www-data /home/student/public_html Next, we must make a few additions to the Apache Configuration File. $ sudo vim /etc/apache2/apache2.conf Add the following lines to the end of apache2.conf <IfModule mod_userdir> UseDir public_html UseDir enabled student <Directory /home/*/public_html> AllowOverride FileInfo AuthConfig Limit Options Indexes SymLinksIfOwnerMatch IncludesNoExec </Directory> </IfModule> These are directives to the Apache Server. The <IfModule mod_userdir> stipulates “If user-web directories are enabled, then do the following”. The next line UseDir public_html indicates that only files in the ‘public_html’ directory of the “~user” should be accessed – essentially notifying Apache of the location of the “~user” files. UseDir enabled student The above directive is a security precaution which stipulates to only allow “student” to have a web directory. Any other “~users” will be disallowed. <Directory /…….> The last directive above are other options for files in the user’s public_html directory. For more information on the provided options, “AllowOverride, FileInfo, AuthConfig, Limit” see the extensive Apache Documentation. http://httpd.apache.org/docs/2.2/mod/core.html#allowoverride http://httpd.apache.org/docs/2.2/howto/public_html.html Next, we must enable user-web directories through the userdir module. This will create two new symbolic links in /etc/apache2/mods-enabled: userdir.conf and userdir.load. To do this you should type in a terminal: $ sudo a2enmod userdir Lastly, we must restart the Apache Server for our changes to take effect. $ sudo /etc/init.d/apache2 restart Open a web-browser and enter “http://localhost/~student” as the URL. Voila! * Do a Print-Screen of the Browser include the URL for Reporting* 4.
Load more

Recommended publications
  • Interfacing Apache HTTP Server 2.4 with External Applications
    Interfacing Apache HTTP Server 2.4 with External Applications Jeff Trawick Interfacing Apache HTTP Server 2.4 with External Applications Jeff Trawick November 6, 2012 Who am I? Interfacing Apache HTTP Server 2.4 with External Applications Met Unix (in the form of Xenix) in 1985 Jeff Trawick Joined IBM in 1990 to work on network software for mainframes Moved to a different organization in 2000 to work on Apache httpd Later spent about 4 years at Sun/Oracle Got tired of being tired of being an employee of too-huge corporation so formed my own too-small company Currently working part-time, coding on other projects, and taking classes Overview Interfacing Apache HTTP Server 2.4 with External Applications Jeff Trawick Huge problem space, so simplify Perspective: \General purpose" web servers, not minimal application containers which implement HTTP \Applications:" Code that runs dynamically on the server during request processing to process input and generate output Possible web server interactions Interfacing Apache HTTP Server 2.4 with External Applications Jeff Trawick Native code plugin modules (uhh, assuming server is native code) Non-native code + language interpreter inside server (Lua, Perl, etc.) Arbitrary processes on the other side of a standard wire protocol like HTTP (proxy), CGI, FastCGI, etc. (Java and \all of the above") or private protocol Some hybrid such as mod fcgid mod fcgid as example hybrid Interfacing Apache HTTP Server 2.4 with External Applications Jeff Trawick Supports applications which implement a standard wire protocol, no restriction on implementation mechanism Has extensive support for managing the application[+interpreter] processes so that the management of the application processes is well-integrated with the web server Contrast with mod proxy fcgi (pure FastCGI, no process management) or mod php (no processes/threads other than those of web server).
    [Show full text]
  • XAMPP Web Development Stack
    XAMPP Web Development Stack Overview @author R.L. Martinez, Ph.D. The steps below outline the processes for installing the XAMPP stack on a local machine. The XAMPP (pronounced Zamp) stack includes the following: Apache HTTP Server, MariaDB (essentially MySQL), Database Server, Perl, and the PHP Interpreter. The “X” in XAMPP is used to signify the cross-platform compatibility of the stack. The Apache HTTP Server and PHP are required to run phpMyAdmin which is a PHP application that is used for database administration tasks such as creating databases and tables, adding users, etc. Alternative to XAMPP If you have experience with MySQL Workbench, you may prefer to install MySQL Server and MySQL Workbench via the MySQL Installer. MySQL Workbench performs the same functions as phpMyAdmin. However, unlike phpMyAdmin which is a web-based application, MySQL Workbench is a locally installed application and therefore does not require an HTTP Server (e.g. Apache) to run. Installing XAMPP Many of the steps listed have several alternatives (such as changing MySQL passwords via a command line) and students are welcomed and encouraged to explore alternatives. 1. Download XAMPP from the URL below and place the installer (.exe) in the location where you want to install XAMPP. Placing the installer (.exe) in the same location as the intended installation is not required but preferred. http://www.apachefriends.org/download.html Page 1 of 17 XAMPP Web Development Stack 2. See the warning which recommends not installing to C:\Program Files (x86) which can be restricted by UAC (User Account Control). In the steps below XAMPP is installed to a USB flash drive for portability.
    [Show full text]
  • Server: Apache
    Modern Trends in Network Fingerprinting SecTor [11.21.07] Jay Graver Ryan Poppa // Fingerprinting Topics Why, What, Who & How? Tools in action Why Tools Break Tools EOL New Approaches New Tool // Why Fingerprint? WhiteHat needs accurate identification of hosts in a PenTest report BlackHat reconnaissance SysAdmins track down and identify new services or hosts when they appear on their network // What is a Fingerprint? Looking at something common … 192.168.2.187:8004 192.168.2.187 [152] 48 54 54 50 2f 31 2e 31 20 32 30 30 20 4f 4b 0d HTTP/1.1 200 OK. 0a 43 6f 6e 6e 65 63 74 69 6f 6e 3a 20 63 6c 6f .Connection: clo 73 65 0d 0a 41 6c 6c 6f 77 3a 20 4f 50 54 49 4f se..Allow: OPTIO 4e 53 2c 20 47 45 54 2c 20 48 45 41 44 2c 20 50 NS, GET, HEAD, P 4f 53 54 0d 0a 43 6f 6e 74 65 6e 74 2d 4c 65 6e OST..Content‐Len 67 74 68 3a 20 30 0d 0a 44 61 74 65 3a 20 46 72 gth: 0..Date: Fr 69 2c 20 30 32 20 4e 6f 76 20 32 30 30 37 20 32 i, 02 Nov 2007 2 32 3a 32 35 3a 31 38 20 47 4d 54 0d 0a 53 65 72 2:25:18 GMT..Ser 76 65 72 3a 20 6c 69 67 68 74 74 70 64 2f 31 2e ver: lighttpd/1. 34 2e 31 35 0d 0a 0d 0a 4.15...
    [Show full text]
  • About Mod Perl Table of Contents
    About mod_perl Table of Contents: About mod_perl General information regarding mod_perl of historical inter- est. Last modified Sun Feb 16 01:38:23 2014 GMT 15 Feb 2014 1 Table of Contents: Part I: Development - 1. The mod_perl Project Management Committee the mod_perl Project Management Committee (PMC) is a group of mod_perl committers who take responsibility for the long-term direction of the project. - 2. mod_perl Contributors A list of people having helped mod_perl along the way, and information about them - 3. Companies sponsoring and supporting mod_perl developers Several companies have contributed to mod_perl by sponsoring mod_perl developers and/or allowing their employees to work on mod_perl as a part of their day job. - 4. Other contributors to mod_perl The other contributions made to mod_perl, that we don’t have enough information on. - 5. History Since mod_perl’s inception in 1996, many things have changed, and it’s interesting to look at mod_perl’s evolution and related events during the time from then to now. Part II: Link to This Site - 6. Link to us A number of banners and buttons that can be used to link to the mod_perl site Part III: mod_perl General Information - 7. How to pronounce mod_perl Do you think that "mod_perl" is a strange name and wondering about how to pronounce it? - 8. License mod_perl is an Apache Software Foundation (http://www.apache.org/) project, licensed under The Apache Software License, an Open Source license. 2 15 Feb 2014 The mod_perl Project Management Committee 1 The mod_perl Project Management Committee 1 The mod_perl Project Management Committee 15 Feb 2014 3 1.1 Description 1.1 Description the mod_perl Project Management Committee (PMC) is a group of mod_perl committers who take respon- sibility for the long-term direction of the project.
    [Show full text]
  • CA SOA Security Manager Agent Configuration Guide
    CA™ SOA Security Manager Agent Configuration Guide r12.1 Second Edition This documentation and any related computer software help programs (hereinafter referred to as the "Documentation") are for your informational purposes only and are subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be used or disclosed by you except as may be permitted in a separate confidentiality agreement between you and CA. Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.
    [Show full text]
  • Licensing Information User Manual Release 9.0 Revision 1.2
    Oracle SD-WAN Edge Licensing Information User Manual Release 9.0 Revision 1.2 October 2020 Licensing Information User Manual Oracle SD-WAN Edge 8.2 Oracle SD-WAN Edge Licensing Information ser !an"al# Release 9.0 Copyright Information $o%yrig't ( 2020# Oracle and)or its a*liates. All rig'ts reser+ed. ,'is soft-are and related doc"mentation are %rovided "nder a license agreement containing restrictions on "se and disclosure and are %rotected by intellect"al %ro%ert& la-s. E.ce%t as e.%ressly %ermitted in &o"r license agreement or allo-ed by la-# &o" may not "se# co%&# re%rod"ce# translate# broadcast# modif&# license# transmit# distrib"te# e.'ibit# %erform# %"blish# or display any %art# in any form# or by any means. Re+erse engineering# disassembl&# or decom%ilation of t'is soft-are# "nless re/"ired by la- for intero%erabilit&# is %ro'ibited. ,'e information contained 'erein is sub0ect to change -it'o"t notice and is not -arranted to be error-free. If &o" find any errors, %lease re%ort t'em to "s in -riting. If t'is is soft-are or related documentation t'at is deli+ered to t'e .S. 2o+ernment or an&one licensing it on be'alf of t'e .S. 2o+ernment# t'en t'e follo-ing notice is a%%licable3 .S. 2O4ERN!EN, END SERS3 Oracle %rograms, incl"ding any o%erating s&stem# integrated soft-are# any %rograms installed on t'e 'ard-are# and)or documentation# deli+ered to .S.
    [Show full text]
  • Escuela T´Ecnica Superior De Ingeniería De
    ESCUELA TECNICA´ SUPERIOR DE INGENIER´IA DE TELECOMUNICACION´ Ingenier´ıa de Telecomunicacion´ PROYECTO FIN DE CARRERA Learning Analytics, Escalabilidad, Mejora de la Experiencia de Usuario e Internacionalizacion´ de la Herramienta de E-Learning FLEQ Autor: Cristina Lavado Arevalo´ Tutor: Gregorio Robles Mart´ınez Curso Acad´emico2013/2014 Proyecto Fin de Carrera LEARNING ANALYTICS, ESCALABILIDAD, MEJORA DE LA EXPERIENCIA DE USUARIO E INTERNACIONALIZACION´ DE LA HERRAMIENTA DE E-LEARNING FLEQ Autor Cristina Lavado Arevalo´ Tutor Gregorio Robles Mart´ınez La defensa del presente Proyecto Fin de Carrera se realiz´oel d´ıa de de , siendo calificada por el siguiente tribunal: PRESIDENTE: SECRETARIO: VOCAL: y habiendo obtenido la siguiente calificaci´on: CALIFICACION:´ Fuenlabrada, a de de . Copyright c 2014 Cristina Lavado Ar´evalo Este documento se publica bajo la licencia Creative Commons Reconocimiento-CompartirIgual 3.0 Espa~na http://creativecommons.org/licenses/by-sa/3.0/es (Ver Ap´endices) A mi familia Agradecimientos Esta´ es la culminaci´onde innumerables experiencias personales, que han dejado en m´ıgrandes recuerdos. Enumerar a todas las personas que me han apoyado e inspirado en estos ´ulti- mos a~noses una tarea incompleta y que voy a revelar ahora. Son muchas las personas a las que tengo que agradecer haber conseguido realizar el sue~node presentar este Proyecto y dar por finalizada una etapa de mi vida de la que me llevo grandes momentos. A los primeros que tengo que dar las gracias es a mi familia, y sobre todo a mis padres, sin vosotros no habr´ıa sido posible, gracias por vuestro apoyo incondicional y vuestro sacrificio durante estos a~nos.Sin la confianza que siempre hab´eisdepositado en m´ı,vuestra sinceridad y consejos este Proyecto y muchos logros personales no habr´ıanvisto la luz.
    [Show full text]
  • Site Map - Apache HTTP Server 2.0
    Site Map - Apache HTTP Server 2.0 Apache HTTP Server Version 2.0 Site Map ● Apache HTTP Server Version 2.0 Documentation ❍ Release Notes ■ Upgrading to 2.0 from 1.3 ■ New features with Apache 2.0 ❍ Using the Apache HTTP Server ■ Compiling and Installing Apache ■ Starting Apache ■ Stopping and Restarting the Server ■ Configuration Files ■ How Directory, Location and Files sections work ■ Server-Wide Configuration ■ Log Files ■ Mapping URLs to Filesystem Locations ■ Security Tips ■ Dynamic Shared Object (DSO) support ■ Content Negotiation ■ Custom error responses ■ Setting which addresses and ports Apache uses ■ Multi-Processing Modules (MPMs) ■ Environment Variables in Apache ■ Apache's Handler Use ■ Filters ■ suEXEC Support ■ Performance Hintes ■ URL Rewriting Guide ❍ Apache Virtual Host documentation ■ Name-based Virtual Hosts ■ IP-based Virtual Host Support ■ Dynamically configured mass virtual hosting ■ VirtualHost Examples ■ An In-Depth Discussion of Virtual Host Matching ■ File descriptor limitations ■ Issues Regarding DNS and Apache ❍ Apache Server Frequently Asked Questions http://httpd.apache.org/docs-2.0/sitemap.html (1 of 4) [5/03/2002 9:53:06 PM] Site Map - Apache HTTP Server 2.0 ■ Support ❍ Apache SSL/TLS Encryption ■ SSL/TLS Encryption: An Introduction ■ SSL/TLS Encryption: Compatibility ■ SSL/TLS Encryption: How-To ■ SSL/TLS Encryption: FAQ ■ SSL/TLS Encryption: Glossary ❍ Guides, Tutorials, and HowTos ■ Authentication ■ Apache Tutorial: Dynamic Content with CGI ■ Apache Tutorial: Introduction to Server Side Includes ■ Apache
    [Show full text]
  • Open Innovation in the Apache Software Foundation
    Open Innovation in The Apache Software Foundation Dr. Justin R. Erenkrantz The Apache Software Foundation TransferSummit/UK http://www.erenkrantz.com/ [email protected] Twitter: @jerenkrantz Friday, June 25, 2010 Why should I pay attention? Committer to Apache HTTP Server, APR, Subversion, and Serf (non-ASF project) President, The Apache Software Foundation Ph.D. from Univ. of California, Irvine Computational REST (next-gen web arch.) http://www.erenkrantz.com/CREST/ CTO, Project WBS 2 Friday, June 25, 2010 Open Source & Me Started contributing to Apache HTTP Server in early 2001... http://www.flickr.com/photos/x180/2704965763/ http://www.flickr.com/photos/bluxte/2103773754/ (James Duncan Davidson) (Sylvain Wallez) 3 Friday, June 25, 2010 Apache Top-level Projects Abdera CXF Karaf Pivot Tika ActiveMQ DB (Derby) Lenya POI Tiles Ant Directory Logging Portals Tomcat APR Excalibur Lucene Qpid Traffic Server Archiva Felix Maven Roller Turbine Avro Forrest Mahout Santuario Tuscany Axis Geronimo Mina ServiceMix UIMA Buildr Gump MyFaces Shindig Velocity Camel Hadoop Nutch Sling Wicket Cassandra Harmony ODE SpamAssassin Web Services Cayenne HBase OFBiz STDCXX Xalan Click HC OpenEJB Struts Xerces Cocoon HTTP Server OpenJPA Subversion XML Commons Jackrabbit OpenWebBeans Synapse XMLBeans Continuum Jakarta PDFBox Tapestry XML Graphics CouchDB James Perl (mod_perl) TCL ...Incubator podlings... 4 Friday, June 25, 2010 Apache’s tagline We are more than a group of projects sharing a server, we are a community of developers and users. 5 Friday, June 25, 2010 Committer geographic diversity http://people.apache.org/map.html Challenges and advantages arise from this! 6 Friday, June 25, 2010 Project Diversity in Apache Seventy top-level projects (TLPs) Java, C, C++, Perl, etc.
    [Show full text]
  • Web Server Administration - the Easy Way
    Chapter 1: What’s In Your Web Site? Get to Know Your Web Server Administrator Web server computer platforms UNIX Macintosh Windows NT Web server software NCSA, W3C/CERN, and Apache Windows NT WebSTAR and MacHTTPD How your Web site fits into the whole Administrator’s jargon and management tools Round Up the Usual Suspects! Inventory Web server resources Take stock of your Web site Lotsa docs (it’s not an M.D.’s convention) Graphics galore The supporting cast of applications… Marvelous miscellany “Organized Web site” is not an oxymoron Where does your site live? Picture your directory/file structure as a tree You can’t tell the territory without a map Understanding all the pieces and parts Using remote hyperlinks What’s the code situation like? Any imagemaps in the picture? Strategic Planning for Your Web Site Juggling large document collections Tooling Up for Web Site Management What tools do you really need? Tool search adventures Judge what you find How to get ’em when you find ’em Wheeling and dealing: what’s your budget? Chapter 2: Web Server Administration - the Easy Way Web Server Hosting Options Web server hosting services Local Web server hosts Web server space renters Web malls Your friendly neighborhood ISP Your organization’s LAN You!? How the Web Server Fits into the Whole The hardware: computer and telephone equipment Web server software and (briefly) how it works The basics Passing information into and out of the HTTP server Web Server Platforms UNIX and the Web Windows (NT and 95) are coming on strong The Macintosh alternative
    [Show full text]
  • Apache Web Server ______
    Apache Web Server _____________________________________________________________________________________________________ Original author(s) Robert McCool Developer(s) Apache Software Foundation Initial release 1995[1] 2.4.9 (March 17, 2014) [±] Stable release Development Active status Written in C, Forth, XML[2] Type Web server License Apache License 2.0 Website httpd.apache.org The Apache HTTP Server , commonly referred to as Apache , is a web server application notable for playing a key role in the initial growth of the World Wide Web.[3] Originally based on the NCSA HTTPd server, development of Apache began in early 1995 after work on the NCSA code stalled. Apache quickly overtook NCSA HTTPd as the dominant HTTP server, and has remained the most popular HTTP server in use since April 1996. In 2009, it became the first web server software to serve more than 100 million websites.[4] Apache is developed and maintained by an open community of developers under the auspices of the Apache Software Foundation. Most commonly used on a Unix-like system,[5] the software is available for a wide variety of operating systems, including Unix, FreeBSD, Linux, Solaris, Novell NetWare, OS X, Microsoft Windows, OS/2, TPF, OpenVMS and eComStation. Released under the Apache License, Apache is open-source software. As of June 2013, Apache was estimated to serve 54.2% of all active websites and 53.3% of the top servers across all domains.[6][7][8][9][10] 1 Apache Web Server _____________________________________________________________________________________________________ Name According to the FAQ in the Apache project website, the name Apache was chosen out of respect to the Native American tribe Apache and its superior skills in warfare and strategy.
    [Show full text]
  • Licensing Information User Manual Mysql Enterprise Monitor 3.4
    Licensing Information User Manual MySQL Enterprise Monitor 3.4 Table of Contents Licensing Information .......................................................................................................................... 4 Licenses for Third-Party Components .................................................................................................. 5 Ant-Contrib ............................................................................................................................... 10 ANTLR 2 .................................................................................................................................. 11 ANTLR 3 .................................................................................................................................. 11 Apache Commons BeanUtils v1.6 ............................................................................................. 12 Apache Commons BeanUtils v1.7.0 and Later ........................................................................... 13 Apache Commons Chain .......................................................................................................... 13 Apache Commons Codec ......................................................................................................... 13 Apache Commons Collections .................................................................................................. 14 Apache Commons Daemon ...................................................................................................... 14 Apache
    [Show full text]