Openfire and JWChat?

Josh9 · October 4, 2007, 12:15am

Hello again all,

I recently got Openfire 3.3.3 up and working fine on my local system. I’m currently trying to figure this with apache, but it doesn’t seem to be working correctly. I’ve found very little useful information on making the two systems play nice together.

I’ve configured the httpd to include a <VirtualHost> entry that looks like this. This is running on localhost.

ServerName localhost

DocumentRoot “C:/mysite/jwchat/”

Options +MultiViews

</Directory>

AddDefaultCharset UTF-8

ProxyPass /http-bind/ http://127.0.0.1:8080/http-bind/http://127.0.0.1:8080/http-bind/

</VirtualHost>

JWChat itself is installed in the directory C:/mysite/jwchat. It’s config file looks like this (config.js)

var SITENAME = “localhost”;

var BACKENDS =

[

];

I can hit localhost:8080 and I see the login for jwchat, however I’m not able to actually log in to jwchat. Is there any support available from openfire to make these two things work together?

Thanks.

Sabine_Dinis_Blochbe · October 4, 2007, 8:46am

csciguy wrote:

Corrected code:

<VirtualHost *>
  ServerName localhost
  DocumentRoot "C:/mysite/jwchat/"
  <Directory "C:/mysite/jwchat/">
    Options +MultiViews
  </Directory>
  AddDefaultCharset UTF-8
  ProxyPass /http-bind/ http://127.0.0.1:8080/http-bind/
</VirtualHost> //---- var SITENAME = "localhost"; var BACKENDS =    [     {       name:"OpenFire",       httpbase:"/http-bind/",       type:"binding",       servers_allowed:[SITENAME]     }   ];

Josh9 · October 9, 2007, 11:16pm

Hi. Thanks for the response. I believe this has gotten me further, however, I am now getting “Service unavailable” when I try to log in to jwchat. Is there anything else I need to do?

Thanks.

Sabine_Dinis_Blochbe · October 10, 2007, 10:58am

Turn on JwChats debugger, and check what the packet says right before the error. It’s either a message from your webserver or OpenFire.

Josh9 · October 14, 2007, 11:36pm

Hi. How do I enable debugging in JWChat?

Sabine_Dinis_Blochbe · October 15, 2007, 9:24am

In the file “config.js” change the lines

/* debugging options */
var DEBUG = true; // turn debugging on
var DEBUG_LVL = 4; // debug-level 0..4 (4 = very noisy) var USE_DEBUGJID = false; // if true only DEBUGJID gets the debugger

just change

var DEBUG=false;

once you’re done.

Edit: you need the files

DebugBottom.html
Debugger.html
Debugger.js
DebugTop.html

for the debugger to work

Josh9 · October 17, 2007, 12:01am

I must have something incorrectly configured still, because after I change those lines, I get nothing.

JWChat is installed in c:\mysite\jwchat. I’ve edited the config.js that lives in that folder. The file looks like this.

/*

JWChat, a web based jabber client

Copyright (C) 2003-2004 Stefan Strigler <steve@zeank.in-berlin.de>

This program is free software; you can redistribute it and/or

modify it under the terms of the GNU General Public License

as published by the Free Software Foundation; either version 2

of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful,

but WITHOUT ANY WARRANTY; without even the implied warranty of

MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the

GNU General Public License for more details.

You should have received a copy of the GNU General Public License

along with this program; if not, write to the Free Software

Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.

Please visit http://jwchat.sourceforge.net for more information!
/
/

This is the main configuration file for the chat client itself.

You have to edit this before you can use jwchat on your website!

Have a look at the README for hints and troubleshooting!
/
var SITENAME = “localhost”;
/ BACKENDS

Array of objects each describing a backend.

Required object fields:

name - human readable short identifier for this backend

httpbase - base address of http service

type - type of backend, must be ‘polling’ or ‘binding’

Optional object fields:

description - a human readable description for this backend

servers_allowed - array of jabber server addresses users can connect to

using this backend

If BACKENDS contains more than one entry users may choose from a

select box which one to use when logging in.

If ‘servers_allowed’ is empty or omitted user is presented an input

field to enter the jabber server to connect to by hand.

If ‘servers_allowed’ contains more than one element user is

presented a select box to choose a jabber server to connect to.

If ‘servers_allowed’ contains one single element no option is

presented to user.
/
var BACKENDS =
[
{
name:“OpenFire”,
httpbase:“/http-bind/”,
type:“binding”,
servers_allowed:[SITENAME]
}
];
/{
name:“Native Polling”,
description:“Ejabberd’s native HTTP Polling backend”,
httpbase:“/http-poll/”,
type:“polling”,
servers_allowed:[SITENAME]
},
{
name:“Open Relay”,
description:“HTTP Binding backend that allows connecting to any jabber server”,
httpbase:“/JHB/”,
type:“binding”,
default_server: SITENAME
},
{
name:“Restricted Relay”,
description:“This one let’s you choose from a limited list of allowed servers”,
httpbase:“/JHB/”,
type:“binding”,
servers_allowed:[http://SITENAME,‘jabber.org’,‘jwchat.org’|http://SITENAME,‘jabber.org’,‘jwchat.o rg’]
},/
var DEFAULTRESOURCE = “jwchat”;
var DEFAULTPRIORITY = “10”;
/ DEFAULTCONFERENCEGROUP + DEFAULTCONFERENCESERVER

default values for joingroupchat form
/
var DEFAULTCONFERENCEROOM = “talks”;
var DEFAULTCONFERENCESERVER = “conference.”+SITENAME;
/ debugging options */
var DEBUG = true; // turn debugging on
var DEBUG_LVL = 4; // debug-level 0…4 (4 = very noisy)
var USE_DEBUGJID = false; // if true only DEBUGJID gets the debugger
var DEBUGJID = “admin@localhost”; // which user get’s debug messages
// most probably you don’t want to change anything below
var timerval = 2000; // poll frequency in msec
var stylesheet = “jwchat.css”;
var THEMESDIR = “themes”;

My httpd.conf looks like this:

This is the main Apache HTTP server configuration file. It contains the

configuration directives that give the server its instructions.

See <URL:Apache HTTP Server Version 2.2 Documentation - Apache HTTP Server Version 2.2> for detailed information.

In particular, see

<URL:Directive Index - Apache HTTP Server Version 2.2>

for a discussion of each configuration directive.

Do NOT simply read the instructions in here without understanding

what they do. They’re here only as hints or reminders. If you are unsure

consult the online docs. You have been warned.

Configuration and logfile names: If the filenames you specify for many

of the server’s control files begin with “/” (or “drive:/” for Win32), the

server will use that explicit path. If the filenames do not begin

with “/”, the value of ServerRoot is prepended – so “logs/foo.log”

with ServerRoot set to “C:/Program Files/Apache Software Foundation/Apache2.2” will be interpreted by the

server as “C:/Program Files/Apache Software Foundation/Apache2.2/logs/foo.log”.

NOTE: Where filenames are specified, you must use forward slashes

instead of backslashes (e.g., “c:/apache” instead of “c:\apache”).

If a drive letter is omitted, the drive on which Apache.exe is located

will be used by default. It is recommended that you always supply

an explicit drive letter in absolute paths, however, to avoid

confusion.

ThreadsPerChild: constant number of worker threads in the server process

MaxRequestsPerChild: maximum number of requests a server process serves

ThreadsPerChild 250
MaxRequestsPerChild 0

ServerRoot: The top of the directory tree under which the server’s

configuration, error, and log files are kept.

Do not add a slash at the end of the directory path. If you point

ServerRoot at a non-local disk, be sure to point the LockFile directive

at a local disk. If you wish to share the same ServerRoot for multiple

httpd daemons, you will need to change at least LockFile and PidFile.

ServerRoot “C:/Program Files/Apache Software Foundation/Apache2.2”

Listen: Allows you to bind Apache to specific IP addresses and/or

ports, instead of the default. See also the <VirtualHost>

directive.

Change this to Listen on specific IP addresses as shown below to

prevent Apache from glomming onto all bound IP addresses (0.0.0.0)

#Listen 12.34.56.78:80
Listen 8080

Dynamic Shared Object (DSO) Support

To be able to use the functionality of a module which was built as a DSO you

have to place corresponding `LoadModule’ lines at this location so the

directives contained in it are actually available before they are used.

Statically compiled modules (those listed by `httpd -l’) do not need

to be loaded here.

Example:

LoadModule foo_module modules/mod_foo.so

LoadModule actions_module modules/mod_actions.so
LoadModule alias_module modules/mod_alias.so
LoadModule asis_module modules/mod_asis.so
LoadModule auth_basic_module modules/mod_auth_basic.so
#LoadModule auth_digest_module modules/mod_auth_digest.so
#LoadModule authn_anon_module modules/mod_authn_anon.so
#LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authn_file_module modules/mod_authn_file.so
#LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule autoindex_module modules/mod_autoindex.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule cgi_module modules/mod_cgi.so
#LoadModule dav_module modules/mod_dav.so
#LoadModule dav_fs_module modules/mod_dav_fs.so
#LoadModule deflate_module modules/mod_deflate.so
LoadModule dir_module modules/mod_dir.so
LoadModule env_module modules/mod_env.so
#LoadModule expires_module modules/mod_expires.so
#LoadModule file_cache_module modules/mod_file_cache.so
#LoadModule headers_module modules/mod_headers.so
LoadModule imagemap_module modules/mod_imagemap.so
LoadModule include_module modules/mod_include.so
#LoadModule info_module modules/mod_info.so
LoadModule isapi_module modules/mod_isapi.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule mime_module modules/mod_mime.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
LoadModule proxy_module modules/mod_proxy.so
#LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
#LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
#LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule proxy_http_module modules/mod_proxy_http.so
#LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule negotiation_module modules/mod_negotiation.so
LoadModule rewrite_module modules/mod_rewrite.so
LoadModule setenvif_module modules/mod_setenvif.so
#LoadModule speling_module modules/mod_speling.so
#LoadModule status_module modules/mod_status.so
#LoadModule unique_id_module modules/mod_unique_id.so
LoadModule userdir_module modules/mod_userdir.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
#LoadModule ssl_module modules/mod_ssl.so

‘Main’ server configuration

The directives in this section set up the values used by the ‘main’

server, which responds to any requests that aren’t handled by a

<VirtualHost> definition. These values also provide defaults for

any <VirtualHost> containers you may define later in the file.

All of these directives may appear inside <VirtualHost> containers,

in which case these default settings will be overridden for the

virtual host being defined.

<VirtualHost *>
ServerName localhost
DocumentRoot “C:/mysite/jwchat/”
<Directory “C:/mysite/jwchat/”>
Options +MultiViews
</Directory>
AddDefaultCharset UTF-8
ProxyPass /http-bind/ http://127.0.0.1:8080/http-bind/
</VirtualHost>

ServerAdmin: Your address, where problems with the server should be

e-mailed. This address appears on some server-generated pages, such

as error documents. e.g. admin@your-domain.com

ServerAdmin none@none.com

ServerName gives the name and port that the server uses to identify itself.

This can often be determined automatically, but we recommend you specify

it explicitly to prevent problems during startup.

If your host doesn’t have a registered DNS name, enter its IP address here.

ServerName localhost:8080

DocumentRoot: The directory out of which you will serve your

documents. By default, all requests are taken from this directory, but

symbolic links and aliases may be used to point to other locations.

DocumentRoot “C:/mysite”

Each directory to which Apache has access can be configured with respect

to which services and features are allowed and/or disabled in that

directory (and its subdirectories).

First, we configure the “default” to be a very restrictive set of

features.

<Directory />
Options FollowSymLinks
AllowOverride None
Order deny,allow
Deny from all
Satisfy all
</Directory>

Note that from this point forward you must specifically allow

particular features to be enabled - so if something’s not working as

you might expect, make sure that you have specifically enabled it

below.

This should be changed to whatever you set DocumentRoot to.

<Directory “C:/mysite”>

Possible values for the Options directive are “None”, “All”,

or any combination of:

Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews

Note that “MultiViews” must be named explicitly — “Options All”

doesn’t give it to you.

The Options directive is both complicated and important. Please see

core - Apache HTTP Server Version 2.2

for more information.

Options Indexes FollowSymLinks

AllowOverride controls what directives may be placed in .htaccess files.

It can be “All”, “None”, or any combination of the keywords:

Options FileInfo AuthConfig Limit

AllowOverride None

Controls who can get stuff from this server.

Order allow,deny
Allow from all
</Directory>

DirectoryIndex: sets the file that Apache will serve if a directory

is requested.

<IfModule dir_module>
DirectoryIndex index.html
</IfModule>

The following lines prevent .htaccess and .htpasswd files from being

viewed by Web clients.

<FilesMatch “^.ht”>
Order allow,deny
Deny from all
</FilesMatch>

ErrorLog: The location of the error log file.

If you do not specify an ErrorLog directive within a <VirtualHost>

container, error messages relating to that virtual host will be

logged here. If you do define an error logfile for a <VirtualHost>

container, that host’s errors will be logged there and not here.

ErrorLog logs/error.log

LogLevel: Control the number of messages logged to the error_log.

Possible values include: debug, info, notice, warn, error, crit,

alert, emerg.

LogLevel warn
<IfModule log_config_module>

The following directives define some format nicknames for use with

a CustomLog directive (see below).

LogFormat “%h %l %u %t "%r" %>s %b "%i" "%{User-Agent}i"” combined
LogFormat “%h %l %u %t "%r" %>s %b” common
<IfModule logio_module>

You need to enable mod_logio.c to use %I and %O

LogFormat “%h %l %u %t "%r" %>s %b "%i" "%{User-Agent}i" %I %O” combinedio
</IfModule>

The location and format of the access logfile (Common Logfile Format).

If you do not define any access logfiles within a <VirtualHost>

container, they will be logged here. Contrariwise, if you do

define per-<VirtualHost> access logfiles, transactions will be

logged therein and not in this file.

CustomLog logs/access.log common

If you prefer a logfile with access, agent, and referer information

(Combined Logfile Format) you can use the following directive.

#CustomLog logs/access.log combined
</IfModule>
<IfModule alias_module>

Redirect: Allows you to tell clients about documents that used to

exist in your server’s namespace, but do not anymore. The client

will make a new request for the document at its new location.

Example:

Redirect permanent /foo http://localhost/bar

Alias: Maps web paths into filesystem paths and is used to

access content that does not live under the DocumentRoot.

Example:

Alias /webpath /full/filesystem/path

If you include a trailing / on /webpath then the server will

require it to be present in the URL. You will also likely

need to provide a <Directory> section to allow access to

the filesystem path.

ScriptAlias: This controls which directories contain server scripts.

ScriptAliases are essentially the same as Aliases, except that

documents in the target directory are treated as applications and

run by the server when requested rather than as documents sent to the

client. The same rules about trailing “/” apply to ScriptAlias

directives as to Alias.

ScriptAlias /cgi-bin/ “C:/Program Files/Apache Software Foundation/Apache2.2/cgi-bin/”
</IfModule>

“C:/Program Files/Apache Software Foundation/Apache2.2/cgi-bin” should be changed to whatever your ScriptAliased

CGI directory exists, if you have that configured.

<Directory “C:/Program Files/Apache Software Foundation/Apache2.2/cgi-bin”>
AllowOverride None
Options None
Order allow,deny
Allow from all
</Directory>
<Directory “/var/www/jwchat”>
AllowOverride All
</Directory>

Apache parses all CGI scripts for the shebang line by default.

This comment line, the first line of the script, consists of the symbols

pound (#) and exclamation followed by the path of the program that

can execute this specific script. For a perl script, with perl.exe in

the C:\Program Files\Perl directory, the shebang line should be:

#!c:/program files/perl/perl

Note you mustnot_ indent the actual shebang line, and it must be the

first line of the file. Of course, CGI processing must be enabled by

the appropriate ScriptAlias or Options ExecCGI directives for the files

or directory in question.

However, Apache on Windows allows either the Unix behavior above, or can

use the Registry to match files by extention. The command to execute

a file of this type is retrieved from the registry by the same method as

the Windows Explorer would use to handle double-clicking on a file.

These script actions can be configured from the Windows Explorer View menu,

‘Folder Options’, and reviewing the ‘File Types’ tab. Clicking the Edit

button allows you to modify the Actions, of which Apache 1.3 attempts to

perform the ‘Open’ Action, and failing that it will try the shebang line.

This behavior is subject to change in Apache release 2.0.

Each mechanism has it’s own specific security weaknesses, from the means

to run a program you didn’t intend the website owner to invoke, and the

best method is a matter of great debate.

To enable the this Windows specific behavior (and therefore -disable- the

equivilant Unix behavior), uncomment the following directive:

#ScriptInterpreterSource registry

The directive above can be placed in individual <Directory> blocks or the

.htaccess file, with either the ‘registry’ (Windows behavior) or ‘script’

(Unix behavior) option, and will override this server default option.

DefaultType: the default MIME type the server will use for a document

if it cannot otherwise determine one, such as from filename extensions.

If your server contains mostly text or HTML documents, “text/plain” is

a good value. If most of your content is binary, such as applications

or images, you may want to use “application/octet-stream” instead to

keep browsers from trying to display binary files as though they are

text.

DefaultType text/plain
<IfModule mime_module>

TypesConfig points to the file containing the list of mappings from

filename extension to MIME-type.

TypesConfig conf/mime.types

AddType allows you to add to or override the MIME configuration

file specified in TypesConfig for specific file types.

#AddType application/x-gzip .tgz

AddEncoding allows you to have certain browsers uncompress

information on the fly. Note: Not all browsers support this.

#AddEncoding x-compress .Z
#AddEncoding x-gzip .gz .tgz

If the AddEncoding directives above are commented-out, then you

probably should define those extensions to indicate media types:

AddType application/x-compress .Z
AddType application/x-gzip .gz .tgz

AddHandler allows you to map certain file extensions to “handlers”:

actions unrelated to filetype. These can be either built into the server

or added with the Action directive (see below)

To use CGI scripts outside of ScriptAliased directories:

(You will also need to add “ExecCGI” to the “Options” directive.)

#AddHandler cgi-script .cgi

For type maps (negotiated resources):

#AddHandler type-map var

Filters allow you to process content before it is sent to the client.

To parse .shtml files for server-side includes (SSI):

(You will also need to add “Includes” to the “Options” directive.)

#AddType text/html .shtml
#AddOutputFilter INCLUDES .shtml
</IfModule>

The mod_mime_magic module allows the server to use various hints from the

contents of the file itself to determine its type. The MIMEMagicFile

directive tells the module where the hint definitions are located.

#MIMEMagicFile conf/magic

Customizable error responses come in three flavors:

1) plain text 2) local redirects 3) external redirects

Some examples:

#ErrorDocument 500 “The server made a boo boo.”
#ErrorDocument 404 /missing.html
#ErrorDocument 404 “/cgi-bin/missing_handler.pl”
#ErrorDocument 402 http://localhost/subscription_info.html

EnableMMAP and EnableSendfile: On systems that support it,

memory-mapping or the sendfile syscall is used to deliver

files. This usually improves server performance, but must

be turned off when serving from networked-mounted

filesystems or if support for these functions is otherwise

broken on your system.

#EnableMMAP off
#EnableSendfile off

Supplemental configuration

The configuration files in the conf/extra/ directory can be

included to add extra features or to modify the default configuration of

the server, or you may simply copy their contents here and change as

necessary.

Server-pool management (MPM specific)

#Include conf/extra/httpd-mpm.conf

Multi-language error messages

#Include conf/extra/httpd-multilang-errordoc.conf

Fancy directory listings

#Include conf/extra/httpd-autoindex.conf

Language settings

#Include conf/extra/httpd-languages.conf

User home directories

#Include conf/extra/httpd-userdir.conf

Real-time info on requests and configuration

#Include conf/extra/httpd-info.conf

Virtual hosts

#Include conf/extra/httpd-vhosts.conf

Local access to the Apache HTTP Server Manual

#Include conf/extra/httpd-manual.conf

Distributed authoring and versioning (WebDAV)

#Include conf/extra/httpd-dav.conf

Various default settings

#Include conf/extra/httpd-default.conf

Secure (SSL/TLS) connections

#Include conf/extra/httpd-ssl.conf

Note: The following must must be present to support

starting without SSL on platforms with no /dev/random equivalent

but a statically compiled-in mod_ssl.

<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>

Everything is run through localhost right now. I can hit http://localhost:8080 and I’m presented with the jwchat login screen. Now when I log in, I get no error messages about “Service unavailable”, however it doesn’t appear that I am logged in. I’ve checked the jwchat directory after turning debugging on and I don’t see any sort of debug log being updated. I’ve restarted both Apache and Openfire multiple times. What else could I be doing wrong here? Are there code tags so I can format this better here next time?

Thanks for your responses.

Sabine_Dinis_Blochbe · October 17, 2007, 8:45am

Ok, I can see at least these issues.

Port 8080 is reserved for OpenFire, Apache has no business listening on it. I would expect OpenFire to write in the error log for not being able to open the port, depending on which server you start first.

If you use localhost as servername, you must set this as OpenFires FQDN, and use JIDs such as joe@localhost

For security, add the following to your VirtualHost paragraph

ProxyRequests Off
  <Proxy *>
    Order deny,allow
    Allow from all
  </Proxy>

Formatting your post is explained in the help (a blue circle with a question mark on it on top of where you write).

Bryan_Tebow · January 9, 2008, 4:11pm

Were you able to find a solution to the “Service unavailable” error? I have prerry much the same setup WAMP/Openfire and I’m also getting the unavailable error.

it0511 · April 1, 2008, 3:08am

My God , There is a " Service Uavailable" TOO!

Please help me!

DEBUG:

(level 2) func: unknown
jid: test@localhost/jwchat
pass: test (level 2) func: unknown
registered handler for event ‘iq’ (level 2) func: unknown
registered handler for event ‘presence’ (level 2) func: unknown
registered handler for event ‘message’ (level 2) func: unknown
registered handler for event ‘message’ (level 2) func: unknown
registered handler for event ‘ondisconnect’ (level 2) func: unknown
registered handler for event ‘onconnect’ (level 2) func: unknown
registered handler for event ‘onerror’ (level 2) func: unknown
httpbase: /http-bind/domain:localhost (level 1) func: unknown
initial response broken (status: 400) (level 2) func: unknown
handling event ‘onerror’

Blue_Light · September 18, 2009, 4:35am

Maybe thi slink helps http://chromus.kajigger.com/blog/2007/03/22/making-jwchat-work-with-openfire/

Openfire and JWChat?

This is the main Apache HTTP server configuration file. It contains the

configuration directives that give the server its instructions.

See <URL:Apache HTTP Server Version 2.2 Documentation - Apache HTTP Server Version 2.2> for detailed information.

In particular, see

<URL:Directive Index - Apache HTTP Server Version 2.2>

for a discussion of each configuration directive.

Do NOT simply read the instructions in here without understanding

what they do. They’re here only as hints or reminders. If you are unsure

consult the online docs. You have been warned.

Configuration and logfile names: If the filenames you specify for many

of the server’s control files begin with “/” (or “drive:/” for Win32), the

server will use that explicit path. If the filenames do not begin

with “/”, the value of ServerRoot is prepended – so “logs/foo.log”

with ServerRoot set to “C:/Program Files/Apache Software Foundation/Apache2.2” will be interpreted by the

server as “C:/Program Files/Apache Software Foundation/Apache2.2/logs/foo.log”.

NOTE: Where filenames are specified, you must use forward slashes

instead of backslashes (e.g., “c:/apache” instead of “c:\apache”).

If a drive letter is omitted, the drive on which Apache.exe is located

will be used by default. It is recommended that you always supply

an explicit drive letter in absolute paths, however, to avoid

confusion.

ThreadsPerChild: constant number of worker threads in the server process

MaxRequestsPerChild: maximum number of requests a server process serves

ServerRoot: The top of the directory tree under which the server’s

configuration, error, and log files are kept.

Do not add a slash at the end of the directory path. If you point

ServerRoot at a non-local disk, be sure to point the LockFile directive

at a local disk. If you wish to share the same ServerRoot for multiple

httpd daemons, you will need to change at least LockFile and PidFile.

Listen: Allows you to bind Apache to specific IP addresses and/or

ports, instead of the default. See also the <VirtualHost>

directive.

Change this to Listen on specific IP addresses as shown below to

prevent Apache from glomming onto all bound IP addresses (0.0.0.0)

Dynamic Shared Object (DSO) Support

To be able to use the functionality of a module which was built as a DSO you

have to place corresponding `LoadModule’ lines at this location so the

directives contained in it are actually available before they are used.

Statically compiled modules (those listed by `httpd -l’) do not need

to be loaded here.

Example:

LoadModule foo_module modules/mod_foo.so

‘Main’ server configuration

The directives in this section set up the values used by the ‘main’

server, which responds to any requests that aren’t handled by a

<VirtualHost> definition. These values also provide defaults for

any <VirtualHost> containers you may define later in the file.

All of these directives may appear inside <VirtualHost> containers,

in which case these default settings will be overridden for the

virtual host being defined.

ServerAdmin: Your address, where problems with the server should be

e-mailed. This address appears on some server-generated pages, such

as error documents. e.g. admin@your-domain.com

ServerName gives the name and port that the server uses to identify itself.

This can often be determined automatically, but we recommend you specify

it explicitly to prevent problems during startup.

If your host doesn’t have a registered DNS name, enter its IP address here.

DocumentRoot: The directory out of which you will serve your

documents. By default, all requests are taken from this directory, but

symbolic links and aliases may be used to point to other locations.

Each directory to which Apache has access can be configured with respect

to which services and features are allowed and/or disabled in that

directory (and its subdirectories).

First, we configure the “default” to be a very restrictive set of

features.

Note that from this point forward you must specifically allow

particular features to be enabled - so if something’s not working as

you might expect, make sure that you have specifically enabled it

below.

This should be changed to whatever you set DocumentRoot to.

Possible values for the Options directive are “None”, “All”,

or any combination of:

Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews

Note that “MultiViews” must be named explicitly — “Options All”

doesn’t give it to you.

The Options directive is both complicated and important. Please see

core - Apache HTTP Server Version 2.2

for more information.

AllowOverride controls what directives may be placed in .htaccess files.