Current Document and Section   Other Documents  
  - Documentation
    - User Guide
  DNS and Domains
Gateway Services Guide
Release Notes
Howtos
 
 

Modules - Web Server

Contents

[edit] Overview

Web Server Information
Description A powerful and popular web server.
Package Name cc-httpd
Configuration Page Software > Web > Web Server


ClarkConnect includes the Apache web server -- the same software that powers many of the world's largest websites.

[edit] Installation

If you did not select this module to be included during the installation process, you must first install the module.

[edit] Configuration

The following documentation is for ClarkConnect 4.2 or later. For previous versions follow this link.

[edit] General

[edit] Global

The basic set-up of the Apache web server is installed by default. In the main configuration, you need to specify two items:

Setup

[edit] Server Name

The server name is a valid name (for example, www.example.com) for your web server. This name is used on some infrequently used error pages, so it is not all that important.

[edit] SSL-Enabled - Secure Site

The web server comes with built-in SSL encryption for enhanced security. If your website requires a username and password for login, then it is a good idea to use enccryption. For instance, if you have the webmail or groupware solution installed, you should access their respective login pages via the secure web server. In your web browser, you should use the encrypted https://your.domain.com instead of the un-encrypted http://your.domain.com (https vs http). When enabled, all communication between the web server and user's web browser is encrypted using a 128-bit security key.

Warning! 
  SSL encryption requires a web site certificate. ClarkConnect automatically generates a default certificate that is 100% secure. However, this certificate is not verified by one of the web site certificate authorities (it costs at least $100 per year to maintain a verified web site certificate). Your users will see the following warning (or similar) when connecting to the secure web server.  
 


SSL Certificate

[edit] Allow FTP Upload

Enables an administrator/user to upload or change content on the website via FTP. By default, the FTP uses a non-standard port of 2121. A user must be created on the server with FTP access in order to provide authentication credentials to login to the FTP server. Any user belonging to the group configured in the Group Access setting will have read/write access to the website directory.

You must use an FTP client (rather than a browser) if you would like to upload files to the server.

[edit] Allow File Server Access

Enables an administrator/user on the LAN (or remotely via VPN) to upload or change content on the website via files shares (SAMBA). To access the share using a Windows client on the LAN, goto "Start Image:Icon_arrowright.png My Computer" and enter:

\\SERVERNAME\DOMAINNAME

Where:

 SERVERNAME = your server's hostname (i.e. webserver.lan)
 DOMAINNAME = your website's domain name (i.e. mywebsite.com)

Any user belonging to the group configured in the Group Access setting will have read/write access to the website directory.

[edit] Group Access

Select a group which will be used to grant access to users who should have access to make modifications (uploads) to the website. If no groups have been created on your server, you will have to add one first before configuring either FTP or file server based access.

[edit] Virtual Hosts

Virtual Hosts

The web server includes support for "virtual hosts". This means your web server can be used for hosting more than one web site.

Virtual Hosts

[edit] Adding Static Content to Your Site

[edit] Text Editor

Not the most efficient means, but certainly possible. Use your favorite text editor and start typing away!

Example:

vi /var/www/html/index.html

And add:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

<html>

 <head>
   <title>My First Web Page</title>
   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
 </head>
 <body>
  <p align="center">Hello World</p>
 </body>

</html>

[edit] Web Design Applications

There are a number of products (free and commercial) to design your own webpages. See the links below for

[edit] Adding Dynamic Content to Your Site

There are many options for adding dynamic content to a website:

  • CGI
  • PHP
  • JSP
  • ASP

The set-up and configuration of these engines are beyond the scope of this help document. PHP, however, is available as a module.

Installing the PHP Module


[edit] Troubleshooting

[edit] ISP Blocking

Some ISPs are known to block web (port 80) traffic to residential broadband connections in an attempt to cut down on illegal sites hosted on their network. If you think your configuration is set-up correctly and you suspect your ISP is blocking HTTP traffic, try a port scan.

[edit] Firewall Rules

A webserver listens to client requests coming in on port 80 (HTTP) or 443 (HTTPS/secure). Did you remember to open the correct port(s)?

[edit] Unable to Gain FTP or File Share Access - Access Denied

If you have just created a user and/or group, try stopping and restarting the FTP and/or file service, depending on which access methods you have configured.

[edit] File Permissions and Third Party Web Applications

It can be tricky configuring the required file permissions on a web application (Mediawiki, Gallery2, Typo3, etc.). Generally speaking, the installed files should be owned by root and readable (not writeable) by apache. You want to avoid giving the web application too much leeway in writing files to disk since that is an extra security risk. Typically, all directories and files are owned by root with read/write permissions, and readable by everyone (read only).

Most web applications will often need to write to disk. For example, a web application installer will typically write a configuration file to disk. For example, the "my_web_app" configuration could be found in /var/www/html/my_web_app/config. In this case, the web server user -- apache should own the file with read/write permissions:

chown apache.root /var/www/html/my_web_app/config


In many web applications, a specific directory is used for writing files. For example, a file upload utility for images is quite common with web applications. The same procedure is the same with directories:

chown apache.root /var/www/html/my_web_app/upload

[edit] Links

Retrieved from "http://www.clarkconnect.com/docs/Modules_-_Web_Server"

This page has been accessed 11,978 times. This page was last modified 17:15, 18 March 2008.