Cherokee Basics
Getting started

Why Cherokee?Feature overview.
RequirementsHardware and software requirements.
DownloadWhere and how to download Cherokee.
InstallationInstallation instructions.
Upgrading CherokeeUpgrading from a previous release?
Running CherokeeBasic steps to run Cherokee.

Configuration
Set up process explained

WalkthroughOverview and walkthrough.
HomeMain section.
StatusServer status information.
GeneralGeneral settings.
Virtual serversServer definition.
Information SourcesDefining information sources.
AdvancedAdvanced tweaking. Not for the faint of heart.
WizardsConfiguration assistants for many known scenarios.

Cookbook
Recipes for specific tasks

AuthenticationHow to set up authenticated resources.
Cross compilationHow to cross compile Cherokee.
DBSlayerHow to set up DBSlayer MySQL balancing.
Embedding CherokeeCherokee on embedded devices.
MaintenanceSeamlessly switching to maintenance mode.
Managing logsSeamless log rotation.
Optimizing CherokeeRecommendations and tweaks.
RedirectionsCommon redirection examples.
SSL/TLS, certsSecure connection tips.
HTTPS acceleratorSSL Offloading with Cherokee.
StreamingHow to stream Audio and Video with Cherokee.
PHPHow to run PHP apps with Cherokee.
Ruby on RailsHow to run Ruby on Rails apps with Cherokee.
DjangoHow to run Django apps with Cherokee.
ColdFusionHow to run ColdFusion apps with Cherokee.
DrupalHow to run Drupal on Cherokee.
WordpressHow to run Wordpress on Cherokee.
AlfrescoHow to run Alfresco on Cherokee.
ASP.NETHow to run ASP.NET apps with Mono and Cherokee.
GlassFishHow to run Java apps with Cherokee.
JoomlaHow to run Joomla on Cherokee.
KumbiaHow to run Kumbia apps with Cherokee.
LiferayHow to run Liferay on Cherokee.
MailmanHow to run Mailman on Cherokee.
MoodleHow to run Moodle on Cherokee.
NagiosHow to run Nagios with Cheroke.
phpBBHow to run phpBB on Cherokee.
phpMyAdminHow to run phpMyAdmin on Cherokee.
SugarCRMHow to run SugarCRM on Cherokee.
Concrete5How to run Concrete5 on Cherokee.
SymfonyHow to run Symfony apps with Cherokee.
TracHow to run Trac on Cherokee.
ZendHow to run Zend apps with Cherokee.
uWSGISetting up Cherokee for uWSGI.
HTTP to HTTPSHow to redirect all traffic from HTTP to HTTPS.
Restricting traffic by IPHow to restrict traffic based on incoming IP.
Domain matchingMatching domains and subdomains with Cherokee.

Modules
Information about the standard modules

HandlersConnection handling modules.
ValidatorsAuthentication mechanisms.
EncodersCompression and filtering.
LoggersLogging mechanisms.
BalancersLoad balancing strategies.

Other information
Miscellaneous

FAQList of Frequently Asked Questions.
Front-line CacheSpecifics of the Caching subsystem.
System TuningTweaking the OS for maximum performance.
Cherokee GoodiesInteresting Cherokee features.
Usage graphsInformation on the several graphs available.
SignalsSignals supported by Cherokee.
CommunityMore information sources.
Common errorsSome typical production errors and their cause.
Man pagesDetails about each program bundled with Cherokee.

Development info
Things of interest to developers

QuickstartWhere to start?
DebuggingResources available to debug Cherokee.
cherokee.confInternal configuration specs.
Quality AssuranceSome info about QA in Cherokee.
CTKDive into the Cherokee Toolkit.

Cherokee’s Distribution
Web Apps distribution on Cherokee

Introduction to DevelopmentHow to build a package.

Documentation

Logger: NCSA

Also known as the Common log format (CLF). This is a standard format produced by many web servers and read by many log analysis tools. Some of the fields specified by the format might actually be missing if the information that should be logged is not present. These fields will simply be replaced by "hyphens" ("-"), which is the standard behavior.

This log format contains only basic HTTP access information: the requested resource and a few other pieces of information, but does not contain referral, user agent, or cookie information.

The fields in the Common log file format are:

 host rfc1413 username date:time request statuscode bytes

A log file produced by this logger will look more or less like this:

::ffff:127.0.0.1 - - [11/Aug/2008:16:17:58 +0000] "GET /index.html HTTP/1.1" 200 2633

Each field of this log entry is described below.

host (::ffff:127.0.0.1): This is the remote host’s IP (the client IP) or host/subdomain. It corresponds to the address of the device requesting the information. If a proxy sever exists between the user and the server, this address will correspond to the proxy instead of the machine actually requesting data.
rfc1413 (-): Missing piece of information. In this case it is the RFC 1413 identity of the client determined by identd on the clients machine, which is highly unreliable and should not be trusted anyway.
user (-): This is the username or UID of the person requesting the document as determined by HTTP authentication. Since the document is not password protected, it is not present in this case. If it is present, the value should not be trusted until the user is actually authenticated.
date:time timezone ([11/Aug/2008:14:18:14 +0000]): The time when the server processed the request. The format is:

[day/month/year:hour:minute:second zone]

+ - day = 2*digit - month = 3*letter - year = 4*digit - hour = 2*digit - minute = 2*digit - second = 2*digit - zone = (‘+’ | ‘-’) 4*digit

request"GET /index.html HTTP/1.1": The request from the client is given in double quotes, and contains the method used by the client (GET), the requested resource (/index.html) and the protocol (HTTP/1.1).
200: Status code sent back to the client. In this case it indicates a successful response. The full list of possible status codes can be found in the HTTP specification (RFC2616, section 10).
2633: The last entry is the size returned to the client excluding the response headers. This will be "-" if no content is returned. To log "0" for no content, use %B instead.