This is a guide to allow someone who wishes to run Apache Web Server, with PHP installed, on a home computer running Windows.
We will cover using it locally on your home network, or optionally setting it up to use on the web, as a private web server.
With a private Web Server you can easily share files with friends and family around the world, or use it for personal access when you travel.
This guide will cover installation and a common configuration to get you up and running as quickly and painlessly as possible.
During this installation, you will be guided through optional configuration of each of the components yourself that most people would care about.
All the other mundane configuration options are done for you, in the httpd.conf, and php.ini files that are provided for you on this page.
You will be guided step by step through only the optional, minimal configuration changes you actually care about or are important!
This will allow you to create a custom tailored Server, and have the basic knowledge to administer your installation yourself!
The Default Configuration files provided "as is" are set to function on a Windows Computer, with a Static IP Address of 192.168.0.10 and with a Folder named www created on Drive C:  (C:\www) for the Servers hosted files.
Using those configuration files "as is", the Server will respond to requests at 192.168.0.10 on Port 80 (Port 80 is a Web Browsers default).

Before you begin, you must make sure your computer has a "Static IP Address".
A Static IP Address is one that NEVER CHANGES!
Since you need to know where your Server is in order to access it, you will need to make sure it is always at one IP Address.
If you already have a Static IP Address (You have the same network IP Address EVERY time you boot your computer), you have options.
If you are using the configuration files provided below "as is", you will want to set your computers Static IP Address to 192.168.0.10.
If you wish to do some minimal editing of the configuration files provided, you can make it whatever suits you as long as it is Static (Never Changes).
If you have decided your option, and already have the appropriate Static IP Address for your choice, you may skip right to Installing Apache Server.
Many home users have a Router which acts as a DHCP Server, assigning them a different IP Address every time they log on.
This can be configured in your Routers Settings, or in your computers Network Settings , depending on your set up, and may require you to edit the settings of both.
If your Router is functioning as a DHCP Server, you will need to reserve an IP Address for your computers specific MAC Address.
This will insure that your computer will ALWAYS be assigned the same IP Address by your Router.

To determine your Computers MAC Address

Enter your Routers Settings, and Reserve an IP Address to your computers MAC Address, in the range of IP Addresses your Router is assigning.

There are too many Routers to cover setting up every one here, so you will have to determine how to do this for your specific Router, or at least make sure your computer always has the same IP Address, before continuing to "Installing Apache Server" below.

NO IIS

That's right you can not run Microsoft  IIS Server and Apache Server at the same time!
If you have IIS installed on your computer, you must remove it, or at least totally disable it! (Removal Recommended!)
This Apache Installation should run on Windows XP and newer Windows operating systems.
PHP Email will be provided by the addition of the Linux sendmail function to Windows. No IIS functions will not be required.

cgi-bin

Create a C:\cgi-bin directory on your Computer.
Open Windows Explorer and Browse to drive C:\ (the Root of drive C)
Right Click on the Right hand side of Windows Explorer, and go to "New", then from the menu that pops out, Left Click on "Folder".
Type "cgi-bin" without the quotes, and press "Enter on your keyboard".
This path will not be hosted by the server, and available to outsiders, so it is secure from hackers being able to drop malicious scripts in your servers cgi-bin directory, and execute them. It is also easy for you to access, when you are developing scripts for your server.

1) Download the latest Apache Server msi file including OpenSSL for Windows, Here: Apache Server Download Page
If you are not sure which file to Download, Use this Direct Download Link to Download the file.

2) Double Click the file to Run the installation Program.

3) Click Next, and accept any license agreements, as you go, and select "Typical" installation type, until you get to the dialog box shown directly below.

4) A dialog box (shown directly below) will appear asking you for your domain name, server name as well as an email address and how to install shortcuts.

A) Where it says "localhost" for Network Domain, and Server Name in the example shown above, use the IP Address of the computer you are installing Apache Server on in both boxes for Network Domain and Server Name. The configuration files below are set to an IP Address of 192.168.0.10 If you have set your computer to a Static IP Address of 192.168.0.10 you WILL NOT need to edit that in the configuration files below for that later.
If you intend to edit the IP Address in the configuration files provided in order to use a different IP Address, you will need your computer to be on that IP Address now, and enter that IP Address in the Network Domain and Server Name boxes.

You can edit the configuration file httpd.conf later on, to change your Servers IP Address, if your Computers IP Address Changes.
B) Enter whatever email address you wish for the email address field.
The installer will use these values to create the default Apache configuration file "hhtp.conf" for you.
C) Choose also to install Apache with shortcuts to start it as a service for all users.

5) Click "Next", as you continue to accept defaults until you get to "Finish".

6) Click Finish.

Note A: After the installation is complete, Apache will Start! You should now notice icon like this in your system tray (by your clock).
This is the Apache Service Monitor. Double clicking it will open up a window, showing the status of your Apache Server, as well as offering you some control over it. This is very handy! When you minimize it it will go back to the tray, until the next time you need it.
If you do not see this icon, or you closed it, and wish to get it back, look in your "All Programs" menu (from your Start Button - Start >> All Programs) for "Apache HTTP Server 2.2".
In the "Apache HTTP Server 2.2" folder, you should see" Monitor Apache Servers".
Click that and the Apache Service Monitor should be back.

Note B: From this point on, expect to see a Warning Pop-Up from your Firewall and / or Antivirus programs, warning you that an application is attempting to access either the internet, or your network. This is to be expected! It will give you the options to Block the application or Allow the application. You MUST select ALLOW in order for your server to function!

7) Test your Installation, and then if all is well, proceed to Configuring Apache Server below!

Open your Web Browser, and type your Computer / Servers IP Address in the address bar after http://
EXAMPLE of what to type in address bar:

http://192.168.0.10

where 192.168.0.10 is replaced with your computers IP Address, if you are setting it up to use a different one.

After entering the information in the Address bar, press "Enter".

When you press "Enter" after typing the Address in the Address bar you should see something like this:

If you see this, Congratulations!!! Apache is installed and functioning!!! It's not ready for use yet!!!
Now lets Install PHP so that the Configuration files for actual use will function, by following the instructions below!

1) Download the latest VC 6 version of PHP for use with Apache 2 for Windows, Here: PHP for Windows Download Page
If you are not sure which file to Download, Use this Direct Download Link to Download the file.
You may need a file extraction utility to extract the zip file into the appropriate directory.
If you do not have a zip file extraction utility, CLICK HERE to download a zip file extraction utility.
If you just finished downloading the zip file extraction utility, install the zip file extraction utility before proceeding.
If you already have a zip file extraction utility installed, you may proceed with PHP installation.

2) Create a php folder in lower case letters, in the Root of Drive C: on the computer Apache Server is installed on ( C:\php ).

3) Run the zip file extraction utility.

4) Open the php zip file in the zip file extraction utility.

5) Extract the contents of the PHP zip file into the C:\php folder you just created.

6) Replace the php.ini file in the C:\php folder with the "Pre-Configured php.ini for Apache and PHP" provided for you to easily make below.

To use this preconfigured php.ini code for use with this Apache Server Installation:

1) Highlight and Copy all the Code in the box directly below.

php.ini

[PHP] ;;;;;;;;;;;;;;;;;;; ; About php.ini ; ;;;;;;;;;;;;;;;;;;; ; This file controls many aspects of PHP's behavior. In order for PHP to ; read it, it must be named 'php.ini'. PHP looks for it in the current ; working directory, in the path designated by the environment variable ; PHPRC, and in the path that was defined in compile time (in that order). ; Under Windows, the compile-time path is the Windows directory. The ; path in which the php.ini file is looked for can be overridden using ; the -c argument in command line mode. ; ; The syntax of the file is extremely simple. Whitespace and Lines ; beginning with a semicolon are silently ignored (as you probably guessed). ; Section headers (e.g. [Foo]) are also silently ignored, even though ; they might mean something in the future. ; ; Directives are specified using the following syntax: ; directive = value ; Directive names are *case sensitive* - foo=bar is different from FOO=bar. ; ; The value can be a string, a number, a PHP constant (e.g. E_ALL or M_PI), one ; of the INI constants (On, Off, True, False, Yes, No and None) or an expression ; (e.g. E_ALL & ~E_NOTICE), or a quoted string ("foo"). ; ; Expressions in the INI file are limited to bitwise operators and parentheses: ; | bitwise OR ; & bitwise AND ; ~ bitwise NOT ; ! boolean NOT ; ; Boolean flags can be turned on using the values 1, On, True or Yes. ; They can be turned off using the values 0, Off, False or No. ; ; An empty string can be denoted by simply not writing anything after the equal ; sign, or by using the None keyword: ; ; foo = ; sets foo to an empty string ; foo = none ; sets foo to an empty string ; foo = "none" ; sets foo to the string 'none' ; ; If you use constants in your value, and these constants belong to a ; dynamically loaded extension (either a PHP extension or a Zend extension), ; you may only use these constants *after* the line that loads the extension. ; ; ;;;;;;;;;;;;;;;;;;; ; About this file ; ;;;;;;;;;;;;;;;;;;; ; This is the recommended, PHP 5-style version of the php.ini-dist file. It ; sets some non standard settings, that make PHP more efficient, more secure, ; and encourage cleaner coding. ; ; The price is that with these settings, PHP may be incompatible with some ; applications, and sometimes, more difficult to develop with. Using this ; file is warmly recommended for production sites. As all of the changes from ; the standard settings are thoroughly documented, you can go over each one, ; and decide whether you want to use it or not. ; ; For general information about the php.ini file, please consult the php.ini-dist ; file, included in your PHP distribution. ; ; This file is different from the php.ini-dist file in the fact that it features ; different values for several directives, in order to improve performance, while ; possibly breaking compatibility with the standard out-of-the-box behavior of ; PHP. Please make sure you read what's different, and modify your scripts ; accordingly, if you decide to use this file instead. ; ; - register_long_arrays = Off [Performance] ; Disables registration of the older (and deprecated) long predefined array ; variables ($HTTP_*_VARS). Instead, use the superglobals that were ; introduced in PHP 4.1.0 ; - display_errors = Off [Security] ; With this directive set to off, errors that occur during the execution of ; scripts will no longer be displayed as a part of the script output, and thus, ; will no longer be exposed to remote users. With some errors, the error message ; content may expose information about your script, web server, or database ; server that may be exploitable for hacking. Production sites should have this ; directive set to off. ; - log_errors = On [Security] ; This directive complements the above one. Any errors that occur during the ; execution of your script will be logged (typically, to your server's error log, ; but can be configured in several ways). Along with setting display_errors to off, ; this setup gives you the ability to fully understand what may have gone wrong, ; without exposing any sensitive information to remote users. ; - output_buffering = 4096 [Performance] ; Set a 4KB output buffer. Enabling output buffering typically results in less ; writes, and sometimes less packets sent on the wire, which can often lead to ; better performance. The gain this directive actually yields greatly depends ; on which Web server you're working with, and what kind of scripts you're using. ; - register_argc_argv = Off [Performance] ; Disables registration of the somewhat redundant $argv and $argc global ; variables. ; - magic_quotes_gpc = Off [Performance] ; Input data is no longer escaped with slashes so that it can be sent into ; SQL databases without further manipulation. Instead, you should use the ; database vendor specific escape string function on each input element you ; wish to send to a database. ; - variables_order = "GPCS" [Performance] ; The environment variables are not hashed into the $_ENV. To access ; environment variables, you can use getenv() instead. ; - error_reporting = E_ALL [Code Cleanliness, Security(?)] ; By default, PHP suppresses errors of type E_NOTICE. These error messages ; are emitted for non-critical errors, but that could be a symptom of a bigger ; problem. Most notably, this will cause error messages about the use ; of uninitialized variables to be displayed. ; - allow_call_time_pass_reference = Off [Code cleanliness] ; It's not possible to decide to force a variable to be passed by reference ; when calling a function. The PHP 4 style to do this is by making the ; function require the relevant argument by reference. ; - short_open_tag = On [Portability] ; Using short tags is discouraged when developing code meant for redistribution ; since short tags may not be supported on the target server. ;;;;;;;;;;;;;;;;;;;; ; Language Options ; ;;;;;;;;;;;;;;;;;;;; ; Enable the PHP scripting language engine under Apache. engine = On ; Enable compatibility mode with Zend Engine 1 (PHP 4.x) zend.ze1_compatibility_mode = Off ; Allow the <? tag. Otherwise, only <?php and <script> tags are recognized. ; NOTE: Using short tags should be avoided when developing applications or ; libraries that are meant for redistribution, or deployment on PHP ; servers which are not under your control, because short tags may not ; be supported on the target server. For portable, redistributable code, ; be sure not to use short tags. short_open_tag = On ; Allow ASP-style <% %> tags. asp_tags = On ; The number of significant digits displayed in floating point numbers. precision = 14 ; Enforce year 2000 compliance (will cause problems with non-compliant browsers) y2k_compliance = On ; Output buffering allows you to send header lines (including cookies) even ; after you send body content, at the price of slowing PHP's output layer a ; bit. You can enable output buffering during runtime by calling the output ; buffering functions. You can also enable output buffering for all files by ; setting this directive to On. If you wish to limit the size of the buffer ; to a certain size - you can use a maximum number of bytes instead of 'On', as ; a value for this directive (e.g., output_buffering=4096). output_buffering = On ; You can redirect all of the output of your scripts to a function. For ; example, if you set output_handler to "mb_output_handler", character ; encoding will be transparently converted to the specified encoding. ; Setting any output handler automatically turns on output buffering. ; Note: People who wrote portable scripts should not depend on this ini ; directive. Instead, explicitly set the output handler using ob_start(). ; Using this ini directive may cause problems unless you know what script ; is doing. ; Note: You cannot use both "mb_output_handler" with "ob_iconv_handler" ; and you cannot use both "ob_gzhandler" and "zlib.output_compression". ; Note: output_handler must be empty if this is set 'On' !!!! ; Instead you must use zlib.output_handler. ;output_handler = ; Transparent output compression using the zlib library ; Valid values for this option are 'off', 'on', or a specific buffer size ; to be used for compression (default is 4KB) ; Note: Resulting chunk size may vary due to nature of compression. PHP ; outputs chunks that are few hundreds bytes each as a result of ; compression. If you prefer a larger chunk size for better ; performance, enable output_buffering in addition. ; Note: You need to use zlib.output_handler instead of the standard ; output_handler, or otherwise the output will be corrupted. zlib.output_compression = Off ;zlib.output_compression_level = -1 ; You cannot specify additional output handlers if zlib.output_compression ; is activated here. This setting does the same as output_handler but in ; a different order. ;zlib.output_handler = ; Implicit flush tells PHP to tell the output layer to flush itself ; automatically after every output block. This is equivalent to calling the ; PHP function flush() after each and every call to print() or echo() and each ; and every HTML block. Turning this option on has serious performance ; implications and is generally recommended for debugging purposes only. implicit_flush = Off ; The unserialize callback function will be called (with the undefined class' ; name as parameter), if the unserializer finds an undefined class ; which should be instantiated. ; A warning appears if the specified function is not defined, or if the ; function doesn't include/implement the missing class. ; So only set this entry, if you really want to implement such a ; callback-function. unserialize_callback_func= ; When floats & doubles are serialized store serialize_precision significant ; digits after the floating point. The default value ensures that when floats ; are decoded with unserialize, the data will remain the same. serialize_precision = 100 ; Whether to enable the ability to force arguments to be passed by reference ; at function call time. This method is deprecated and is likely to be ; unsupported in future versions of PHP/Zend. The encouraged method of ; specifying which arguments should be passed by reference is in the function ; declaration. You're encouraged to try and turn this option Off and make ; sure your scripts work properly with it in order to ensure they will work ; with future versions of the language (you will receive a warning each time ; you use this feature, and the argument will be passed by value instead of by ; reference). allow_call_time_pass_reference = Off ; ; Safe Mode ; safe_mode = Off ; By default, Safe Mode does a UID compare check when ; opening files. If you want to relax this to a GID compare, ; then turn on safe_mode_gid. safe_mode_gid = Off ; When safe_mode is on, UID/GID checks are bypassed when ; including files from this directory and its subdirectories. ; (directory must also be in include_path or full path must ; be used when including) safe_mode_include_dir = ; When safe_mode is on, only executables located in the safe_mode_exec_dir ; will be allowed to be executed via the exec family of functions. safe_mode_exec_dir = ; Setting certain environment variables may be a potential security breach. ; This directive contains a comma-delimited list of prefixes. In Safe Mode, ; the user may only alter environment variables whose names begin with the ; prefixes supplied here. By default, users will only be able to set ; environment variables that begin with PHP_ (e.g. PHP_FOO=BAR). ; ; Note: If this directive is empty, PHP will let the user modify ANY ; environment variable! safe_mode_allowed_env_vars = PHP_ ; This directive contains a comma-delimited list of environment variables that ; the end user won't be able to change using putenv(). These variables will be ; protected even if safe_mode_allowed_env_vars is set to allow to change them. safe_mode_protected_env_vars = LD_LIBRARY_PATH ; open_basedir, if set, limits all file operations to the defined directory ; and below. This directive makes most sense if used in a per-directory ; or per-virtualhost web server configuration file. This directive is ; *NOT* affected by whether Safe Mode is turned On or Off. ;open_basedir = ; This directive allows you to disable certain functions for security reasons. ; It receives a comma-delimited list of function names. This directive is ; *NOT* affected by whether Safe Mode is turned On or Off. disable_functions = ; This directive allows you to disable certain classes for security reasons. ; It receives a comma-delimited list of class names. This directive is ; *NOT* affected by whether Safe Mode is turned On or Off. disable_classes = ; Colors for Syntax Highlighting mode. Anything that's acceptable in ; <span style="color: ???????"> would work. ;highlight.string = #DD0000 ;highlight.comment = #FF9900 ;highlight.keyword = #007700 ;highlight.bg = #FFFFFF ;highlight.default = #0000BB ;highlight.html = #000000 ; If enabled, the request will be allowed to complete even if the user aborts ; the request. Consider enabling it if executing long request, which may end up ; being interrupted by the user or a browser timing out. ; ignore_user_abort = On ; Determines the size of the realpath cache to be used by PHP. This value should ; be increased on systems where PHP opens many files to reflect the quantity of ; the file operations performed. ; realpath_cache_size=16k ; Duration of time, in seconds for which to cache realpath information for a given ; file or directory. For systems with rarely changing files, consider increasing this ; value. ; realpath_cache_ttl=120 ; ; Misc ; ; Decides whether PHP may expose the fact that it is installed on the server ; (e.g. by adding its signature to the Web server header). It is no security ; threat in any way, but it makes it possible to determine whether you use PHP ; on your server or not. expose_php = On ;;;;;;;;;;;;;;;;;;; ; Resource Limits ; ;;;;;;;;;;;;;;;;;;; max_execution_time = 30 ; Maximum execution time of each script, in seconds max_input_time = 60 ; Maximum amount of time each script may spend parsing request data ;max_input_nesting_level = 64 ; Maximum input variable nesting level memory_limit = 128M ; Maximum amount of memory a script may consume (128MB) ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; Error handling and logging ; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; error_reporting is a bit-field. Or each number up to get desired error ; reporting level ; E_ALL - All errors and warnings (doesn't include E_STRICT) ; E_ERROR - fatal run-time errors ; E_RECOVERABLE_ERROR - almost fatal run-time errors ; E_WARNING - run-time warnings (non-fatal errors) ; E_PARSE - compile-time parse errors ; E_NOTICE - run-time notices (these are warnings which often result ; from a bug in your code, but it's possible that it was ; intentional (e.g., using an uninitialized variable and ; relying on the fact it's automatically initialized to an ; empty string) ; E_STRICT - run-time notices, enable to have PHP suggest changes ; to your code which will ensure the best interoperability ; and forward compatibility of your code ; E_CORE_ERROR - fatal errors that occur during PHP's initial startup ; E_CORE_WARNING - warnings (non-fatal errors) that occur during PHP's ; initial startup ; E_COMPILE_ERROR - fatal compile-time errors ; E_COMPILE_WARNING - compile-time warnings (non-fatal errors) ; E_USER_ERROR - user-generated error message ; E_USER_WARNING - user-generated warning message ; E_USER_NOTICE - user-generated notice message ; ; Examples: ; ; - Show all errors, except for notices and coding standards warnings ; ;error_reporting = E_ALL & ~E_NOTICE ; ; - Show all errors, except for notices ; ;error_reporting = E_ALL & ~E_NOTICE | E_STRICT ; ; - Show only errors ; ;error_reporting = E_COMPILE_ERROR|E_RECOVERABLE_ERROR|E_ERROR|E_CORE_ERROR ; ; - Show all errors, except coding standards warnings ; error_reporting = E_ALL ; Print out errors (as a part of the output). For production web sites, ; you're strongly encouraged to turn this feature off, and use error logging ; instead (see below). Keeping display_errors enabled on a production web site ; may reveal security information to end users, such as file paths on your Web ; server, your database schema or other information. ; ; possible values for display_errors: ; ; Off - Do not display any errors ; stderr - Display errors to STDERR (affects only CGI/CLI binaries!) ; On or stdout - Display errors to STDOUT (default) ; ; To output errors to STDERR with CGI/CLI: ;display_errors = "stderr" ; ; Default ; display_errors = Off ; Even when display_errors is on, errors that occur during PHP's startup ; sequence are not displayed. It's strongly recommended to keep ; display_startup_errors off, except for when debugging. display_startup_errors = Off ; Log errors into a log file (server-specific log, stderr, or error_log (below)) ; As stated above, you're strongly advised to use error logging in place of ; error displaying on production web sites. log_errors = On ; Set maximum length of log_errors. In error_log information about the source is ; added. The default is 1024 and 0 allows to not apply any maximum length at all. log_errors_max_len = 1024 ; Do not log repeated messages. Repeated errors must occur in same file on same ; line unless ignore_repeated_source is set true. ignore_repeated_errors = Off ; Ignore source of message when ignoring repeated messages. When this setting ; is On you will not log errors with repeated messages from different files or ; source lines. ignore_repeated_source = Off ; If this parameter is set to Off, then memory leaks will not be shown (on ; stdout or in the log). This has only effect in a debug compile, and if ; error reporting includes E_WARNING in the allowed list report_memleaks = On ;report_zend_debug = 0 ; Store the last error/warning message in $php_errormsg (boolean). track_errors = Off ; Turn off normal error reporting and emit XML-RPC error XML ;xmlrpc_errors = 0 ; An XML-RPC faultCode ;xmlrpc_error_number = 0 ; Disable the inclusion of HTML tags in error messages. ; Note: Never use this feature for production boxes. ;html_errors = Off ; If html_errors is set On PHP produces clickable error messages that direct ; to a page describing the error or function causing the error in detail. ; You can download a copy of the PHP manual from http://www.php.net/docs.php ; and change docref_root to the base URL of your local copy including the ; leading '/'. You must also specify the file extension being used including ; the dot. ; Note: Never use this feature for production boxes. ;docref_root = "/phpmanual/" ;docref_ext = .html ; String to output before an error message. ;error_prepend_string = "<font color=#ff0000>" ; String to output after an error message. ;error_append_string = "</font>" ; Log errors to specified file. ;error_log = filename ; Log errors to syslog (Event Log on NT, not valid in Windows 95). ;error_log = syslog ;;;;;;;;;;;;;;;;; ; Data Handling ; ;;;;;;;;;;;;;;;;; ; ; Note - track_vars is ALWAYS enabled as of PHP 4.0.3 ; The separator used in PHP generated URLs to separate arguments. ; Default is "&". ;arg_separator.output = "&" ; List of separator(s) used by PHP to parse input URLs into variables. ; Default is "&". ; NOTE: Every character in this directive is considered as separator! ;arg_separator.input = ";&" ; This directive describes the order in which PHP registers GET, POST, Cookie, ; Environment and Built-in variables (G, P, C, E & S respectively, often ; referred to as EGPCS or GPC). Registration is done from left to right, newer ; values override older values. variables_order = "GPCS" ; Whether or not to register the EGPCS variables as global variables. You may ; want to turn this off if you don't want to clutter your scripts' global scope ; with user data. This makes most sense when coupled with track_vars - in which ; case you can access all of the GPC variables through the $HTTP_*_VARS[], ; variables. ; ; You should do your best to write your scripts so that they do not require ; register_globals to be on; Using form variables as globals can easily lead ; to possible security problems, if the code is not very well thought of. register_globals = On ; Whether or not to register the old-style input arrays, HTTP_GET_VARS ; and friends. If you're not using them, it's recommended to turn them off, ; for performance reasons. register_long_arrays = Off ; This directive tells PHP whether to declare the argv&argc variables (that ; would contain the GET information). If you don't use these variables, you ; should turn it off for increased performance. register_argc_argv = Off ; When enabled, the SERVER and ENV variables are created when they're first ; used (Just In Time) instead of when the script starts. If these variables ; are not used within a script, having this directive on will result in a ; performance gain. The PHP directives register_globals, register_long_arrays, ; and register_argc_argv must be disabled for this directive to have any affect. auto_globals_jit = On ; Maximum size of POST data that PHP will accept. post_max_size = 8M ; Magic quotes ; ; Magic quotes for incoming GET/POST/Cookie data. magic_quotes_gpc = On ; Magic quotes for runtime-generated data, e.g. data from SQL, from exec(), etc. magic_quotes_runtime = Off ; Use Sybase-style magic quotes (escape ' with '' instead of \'). magic_quotes_sybase = Off ; Automatically add files before or after any PHP document. auto_prepend_file = auto_append_file = ; As of 4.0b4, PHP always outputs a character encoding by default in ; the Content-type: header. To disable sending of the charset, simply ; set it to be empty. ; ; PHP's built-in default is text/html default_mimetype = "text/html" ;default_charset = "iso-8859-1" ; Always populate the $HTTP_RAW_POST_DATA variable. ;always_populate_raw_post_data = On ;;;;;;;;;;;;;;;;;;;;;;;;; ; Paths and Directories ; ;;;;;;;;;;;;;;;;;;;;;;;;; ; UNIX: "/path1:/path2" ;include_path = ".:/php/includes" ; ; Windows: "\path1;\path2" ;include_path = ".;c:\php\includes" ; The root of the PHP pages, used only if nonempty. ; if PHP was not compiled with FORCE_REDIRECT, you SHOULD set doc_root ; if you are running php as a CGI under any web server (other than IIS) ; see documentation for security issues. The alternate is to use the ; cgi.force_redirect configuration below doc_root = ; The directory under which PHP opens the script using /~username used only ; if nonempty. user_dir = ; Directory in which the loadable extensions (modules) reside. ;extension_dir = "./" extension_dir = C:\php\ext ; Whether or not to enable the dl() function. The dl() function does NOT work ; properly in multithreaded servers, such as IIS or Zeus, and is automatically ; disabled on them. enable_dl = On ; cgi.force_redirect is necessary to provide security running PHP as a CGI under ; most web servers. Left undefined, PHP turns this on by default. You can ; turn it off here AT YOUR OWN RISK ; **You CAN safely turn this off for IIS, in fact, you MUST.** ; cgi.force_redirect = 1 ; if cgi.nph is enabled it will force cgi to always sent Status: 200 with ; every request. ; cgi.nph = 1 ; if cgi.force_redirect is turned on, and you are not running under Apache or Netscape ; (iPlanet) web servers, you MAY need to set an environment variable name that PHP ; will look for to know it is OK to continue execution. Setting this variable MAY ; cause security issues, KNOW WHAT YOU ARE DOING FIRST. ; cgi.redirect_status_env = ; ; cgi.fix_pathinfo provides *real* PATH_INFO/PATH_TRANSLATED support for CGI. PHP's ; previous behaviour was to set PATH_TRANSLATED to SCRIPT_FILENAME, and to not grok ; what PATH_INFO is. For more information on PATH_INFO, see the cgi specs. Setting ; this to 1 will cause PHP CGI to fix it's paths to conform to the spec. A setting ; of zero causes PHP to behave as before. Default is 1. You should fix your scripts ; to use SCRIPT_FILENAME rather than PATH_TRANSLATED. ; cgi.fix_pathinfo=1 ; FastCGI under IIS (on WINNT based OS) supports the ability to impersonate ; security tokens of the calling client. This allows IIS to define the ; security context that the request runs under. mod_fastcgi under Apache ; does not currently support this feature (03/17/2002) ; Set to 1 if running under IIS. Default is zero. ; fastcgi.impersonate = 1; ; Disable logging through FastCGI connection ; fastcgi.logging = 0 ; cgi.rfc2616_headers configuration option tells PHP what type of headers to ; use when sending HTTP response code. If it's set 0 PHP sends Status: header that ; is supported by Apache. When this option is set to 1 PHP will send ; RFC2616 compliant header. ; Default is zero. ;cgi.rfc2616_headers = 0 ;;;;;;;;;;;;;;;; ; File Uploads ; ;;;;;;;;;;;;;;;; ; Whether to allow HTTP file uploads. file_uploads = On ; Temporary directory for HTTP uploaded files (will use system default if not ; specified). ;upload_tmp_dir = ; Maximum allowed size for uploaded files. upload_max_filesize = 30M ; Maximum number of files that can be uploaded via a single request max_file_uploads = 30 ;;;;;;;;;;;;;;;;;; ; Fopen wrappers ; ;;;;;;;;;;;;;;;;;; ; Whether to allow the treatment of URLs (like http:// or ftp://) as files. allow_url_fopen = On ; Whether to allow include/require to open URLs (like http:// or ftp://) as files. allow_url_include = Off ; Define the anonymous ftp password (your email address) ;from="john@doe.com" ; Define the User-Agent string ; user_agent="PHP" ; Default timeout for socket based streams (seconds) default_socket_timeout = 60 ; If your scripts have to deal with files from Macintosh systems, ; or you are running on a Mac and need to deal with files from ; unix or win32 systems, setting this flag will cause PHP to ; automatically detect the EOL character in those files so that ; fgets() and file() will work regardless of the source of the file. ; auto_detect_line_endings = Off ;;;;;;;;;;;;;;;;;;;;;; ; Dynamic Extensions ; ;;;;;;;;;;;;;;;;;;;;;; ; ; If you wish to have an extension loaded automatically, use the following ; syntax: ; ; extension=modulename.extension ; ; For example, on Windows: ; ; extension=msql.dll ; ; ... or under UNIX: ; ; extension=msql.so ; ; Note that it should be the name of the module only; no directory information ; needs to go here. Specify the location of the extension with the ; extension_dir directive above. ; Windows Extensions ; Note that ODBC support is built in, so no dll is needed for it. ; Note that many DLL files are located in the extensions/ (PHP 4) ext/ (PHP 5) ; extension folders as well as the separate PECL DLL download (PHP 5). ; Be sure to appropriately set the extension_dir directive. extension=php_bz2.dll extension=php_curl.dll extension=php_dba.dll extension=php_dbase.dll ;extension=php_fdf.dll extension=php_gd2.dll extension=php_gettext.dll extension=php_gmp.dll ;extension=php_ifx.dll extension=php_imap.dll ;extension=php_interbase.dll extension=php_ldap.dll extension=php_mbstring.dll extension=php_exif.dll extension=php_mcrypt.dll extension=php_mhash.dll ;extension=php_mime_magic.dll ;extension=php_ming.dll ;extension=php_msql.dll ;extension=php_mssql.dll ;extension=php_mysql.dll ;extension=php_mysqli.dll ;extension=php_oci8.dll extension=php_openssl.dll extension=php_pdo.dll ;extension=php_pdo_firebird.dll ;extension=php_pdo_mssql.dll ;extension=php_pdo_mysql.dll ;extension=php_pdo_oci.dll ;extension=php_pdo_oci8.dll ;extension=php_pdo_odbc.dll extension=php_pdo_pgsql.dll extension=php_pdo_sqlite.dll extension=php_pgsql.dll extension=php_pspell.dll extension=php_shmop.dll ;extension=php_snmp.dll extension=php_soap.dll extension=php_sockets.dll extension=php_sqlite.dll ;extension=php_sybase_ct.dll extension=php_tidy.dll extension=php_xmlrpc.dll extension=php_xsl.dll extension=php_zip.dll ;;;;;;;;;;;;;;;;;;; ; Module Settings ; ;;;;;;;;;;;;;;;;;;; [Date] ; Defines the default timezone used by the date functions ;date.timezone = America/New_York ;date.default_latitude = 26.224000 ;date.default_longitude = -80.173433 ;date.sunrise_zenith = 90.583333 ;date.sunset_zenith = 90.583333 [filter] ;filter.default = unsafe_raw ;filter.default_flags = [iconv] ;iconv.input_encoding = ISO-8859-1 ;iconv.internal_encoding = ISO-8859-1 ;iconv.output_encoding = ISO-8859-1 [sqlite] ;sqlite.assoc_case = 0 [Pcre] ;PCRE library backtracking limit. ;pcre.backtrack_limit=100000 ;PCRE library recursion limit. ;Please note that if you set this value to a high number you may consume all ;the available process stack and eventually crash PHP (due to reaching the ;stack size limit imposed by the Operating System). ;pcre.recursion_limit=100000 [Syslog] ; Whether or not to define the various syslog variables (e.g. $LOG_PID, ; $LOG_CRON, etc.). Turning it off is a good idea performance-wise. In ; runtime, you can define these variables by calling define_syslog_variables(). define_syslog_variables = Off [mail function] ; For Win32 only. ;SMTP = localhost ;mail.mydomain.com ;smtp_port = 25 ; For Win32 only. ;sendmail_from = webmaster@mydomain.com ; For Unix only. You may supply arguments as well (default: "sendmail -t -i"). sendmail_path = C:\sendmail\sendmail.exe ; Force the addition of the specified parameters to be passed as extra parameters ; to the sendmail binary. These parameters will always replace the value of ; the 5th parameter to mail(), even in safe mode. ;mail.force_extra_parameters = [SQL] sql.safe_mode = Off [ODBC] ;odbc.default_db = Not yet implemented ;odbc.default_user = Not yet implemented ;odbc.default_pw = Not yet implemented ; Allow or prevent persistent links. odbc.allow_persistent = On ; Check that a connection is still valid before reuse. odbc.check_persistent = On ; Maximum number of persistent links. -1 means no limit. odbc.max_persistent = -1 ; Maximum number of links (persistent + non-persistent). -1 means no limit. odbc.max_links = -1 ; Handling of LONG fields. Returns number of bytes to variables. 0 means ; passthru. odbc.defaultlrl = 4096 ; Handling of binary data. 0 means passthru, 1 return as is, 2 convert to char. ; See the documentation on odbc_binmode and odbc_longreadlen for an explanation ; of uodbc.defaultlrl and uodbc.defaultbinmode odbc.defaultbinmode = 1 [MySQL] ; Allow or prevent persistent links. mysql.allow_persistent = On ; Maximum number of persistent links. -1 means no limit. mysql.max_persistent = -1 ; Maximum number of links (persistent + non-persistent). -1 means no limit. mysql.max_links = -1 ; Default port number for mysql_connect(). If unset, mysql_connect() will use ; the $MYSQL_TCP_PORT or the mysql-tcp entry in /etc/services or the ; compile-time value defined MYSQL_PORT (in that order). Win32 will only look ; at MYSQL_PORT. mysql.default_port = ; Default socket name for local MySQL connects. If empty, uses the built-in ; MySQL defaults. mysql.default_socket = ; Default host for mysql_connect() (doesn't apply in safe mode). mysql.default_host = ; Default user for mysql_connect() (doesn't apply in safe mode). mysql.default_user = ; Default password for mysql_connect() (doesn't apply in safe mode). ; Note that this is generally a *bad* idea to store passwords in this file. ; *Any* user with PHP access can run 'echo get_cfg_var("mysql.default_password") ; and reveal this password! And of course, any users with read access to this ; file will be able to reveal the password as well. mysql.default_password = ; Maximum time (in seconds) for connect timeout. -1 means no limit mysql.connect_timeout = 60 ; Trace mode. When trace_mode is active (=On), warnings for table/index scans and ; SQL-Errors will be displayed. mysql.trace_mode = Off [MySQLi] ; Maximum number of links. -1 means no limit. mysqli.max_links = -1 ; Default port number for mysqli_connect(). If unset, mysqli_connect() will use ; the $MYSQL_TCP_PORT or the mysql-tcp entry in /etc/services or the ; compile-time value defined MYSQL_PORT (in that order). Win32 will only look ; at MYSQL_PORT. mysqli.default_port = 3306 ; Default socket name for local MySQL connects. If empty, uses the built-in ; MySQL defaults. mysqli.default_socket = ; Default host for mysql_connect() (doesn't apply in safe mode). mysqli.default_host = ; Default user for mysql_connect() (doesn't apply in safe mode). mysqli.default_user = ; Default password for mysqli_connect() (doesn't apply in safe mode). ; Note that this is generally a *bad* idea to store passwords in this file. ; *Any* user with PHP access can run 'echo get_cfg_var("mysqli.default_pw") ; and reveal this password! And of course, any users with read access to this ; file will be able to reveal the password as well. mysqli.default_pw = ; Allow or prevent reconnect mysqli.reconnect = Off [mSQL] ; Allow or prevent persistent links. msql.allow_persistent = On ; Maximum number of persistent links. -1 means no limit. msql.max_persistent = -1 ; Maximum number of links (persistent+non persistent). -1 means no limit. msql.max_links = -1 [OCI8] ; enables privileged connections using external credentials (OCI_SYSOPER, OCI_SYSDBA) ;oci8.privileged_connect = Off ; Connection: The maximum number of persistent OCI8 connections per ; process. Using -1 means no limit. ;oci8.max_persistent = -1 ; Connection: The maximum number of seconds a process is allowed to ; maintain an idle persistent connection. Using -1 means idle ; persistent connections will be maintained forever. ;oci8.persistent_timeout = -1 ; Connection: The number of seconds that must pass before issuing a ; ping during oci_pconnect() to check the connection validity. When ; set to 0, each oci_pconnect() will cause a ping. Using -1 disables ; pings completely. ;oci8.ping_interval = 60 ; Tuning: This option enables statement caching, and specifies how ; many statements to cache. Using 0 disables statement caching. ;oci8.statement_cache_size = 20 ; Tuning: Enables statement prefetching and sets the default number of ; rows that will be fetched automatically after statement execution. ;oci8.default_prefetch = 10 ; Compatibility. Using On means oci_close() will not close ; oci_connect() and oci_new_connect() connections. ;oci8.old_oci_close_semantics = Off [PostgresSQL] ; Allow or prevent persistent links. pgsql.allow_persistent = On ; Detect broken persistent links always with pg_pconnect(). ; Auto reset feature requires a little overheads. pgsql.auto_reset_persistent = Off ; Maximum number of persistent links. -1 means no limit. pgsql.max_persistent = -1 ; Maximum number of links (persistent+non persistent). -1 means no limit. pgsql.max_links = -1 ; Ignore PostgreSQL backends Notice message or not. ; Notice message logging require a little overheads. pgsql.ignore_notice = 0 ; Log PostgreSQL backends Notice message or not. ; Unless pgsql.ignore_notice=0, module cannot log notice message. pgsql.log_notice = 0 [Sybase] ; Allow or prevent persistent links. sybase.allow_persistent = On ; Maximum number of persistent links. -1 means no limit. sybase.max_persistent = -1 ; Maximum number of links (persistent + non-persistent). -1 means no limit. sybase.max_links = -1 ;sybase.interface_file = "/usr/sybase/interfaces" ; Minimum error severity to display. sybase.min_error_severity = 10 ; Minimum message severity to display. sybase.min_message_severity = 10 ; Compatibility mode with old versions of PHP 3.0. ; If on, this will cause PHP to automatically assign types to results according ; to their Sybase type, instead of treating them all as strings. This ; compatibility mode will probably not stay around forever, so try applying ; whatever necessary changes to your code, and turn it off. sybase.compatability_mode = Off [Sybase-CT] ; Allow or prevent persistent links. sybct.allow_persistent = On ; Maximum number of persistent links. -1 means no limit. sybct.max_persistent = -1 ; Maximum number of links (persistent + non-persistent). -1 means no limit. sybct.max_links = -1 ; Minimum server message severity to display. sybct.min_server_severity = 10 ; Minimum client message severity to display. sybct.min_client_severity = 10 [bcmath] ; Number of decimal digits for all bcmath functions. bcmath.scale = 0 [browscap] ;browscap = extra/browscap.ini [Informix] ; Default host for ifx_connect() (doesn't apply in safe mode). ifx.default_host = ; Default user for ifx_connect() (doesn't apply in safe mode). ifx.default_user = ; Default password for ifx_connect() (doesn't apply in safe mode). ifx.default_password = ; Allow or prevent persistent links. ifx.allow_persistent = On ; Maximum number of persistent links. -1 means no limit. ifx.max_persistent = -1 ; Maximum number of links (persistent + non-persistent). -1 means no limit. ifx.max_links = -1 ; If on, select statements return the contents of a text blob instead of its id. ifx.textasvarchar = 0 ; If on, select statements return the contents of a byte blob instead of its id. ifx.byteasvarchar = 0 ; Trailing blanks are stripped from fixed-length char columns. May help the ; life of Informix SE users. ifx.charasvarchar = 0 ; If on, the contents of text and byte blobs are dumped to a file instead of ; keeping them in memory. ifx.blobinfile = 0 ; NULL's are returned as empty strings, unless this is set to 1. In that case, ; NULL's are returned as string 'NULL'. ifx.nullformat = 0 [Session] ; Handler used to store/retrieve data. session.save_handler = files ; Argument passed to save_handler. In the case of files, this is the path ; where data files are stored. Note: Windows users have to change this ; variable in order to use PHP's session functions. ; ; As of PHP 4.0.1, you can define the path as: ; ; session.save_path = "N;/path" ; ; where N is an integer. Instead of storing all the session files in ; /path, what this will do is use subdirectories N-levels deep, and ; store the session data in those directories. This is useful if you ; or your OS have problems with lots of files in one directory, and is ; a more efficient layout for servers that handle lots of sessions. ; ; NOTE 1: PHP will not create this directory structure automatically. ; You can use the script in the ext/session dir for that purpose. ; NOTE 2: See the section on garbage collection below if you choose to ; use subdirectories for session storage ; ; The file storage module creates files using mode 600 by default. ; You can change that by using ; ; session.save_path = "N;MODE;/path" ; ; where MODE is the octal representation of the mode. Note that this ; does not overwrite the process's umask. session.save_path = "E:/sessions" ; Whether to use cookies. session.use_cookies = 1 ;session.cookie_secure = ; This option enables administrators to make their users invulnerable to ; attacks which involve passing session ids in URLs; defaults to 0. ; session.use_only_cookies = 1 ; Name of the session (used as cookie name). session.name = PHPSESSID ; Initialize session on request startup. session.auto_start = 0 ; Lifetime in seconds of cookie or, if 0, until browser is restarted. session.cookie_lifetime = 0 ; The path for which the cookie is valid. session.cookie_path = / ; The domain for which the cookie is valid. session.cookie_domain = ; Whether or not to add the httpOnly flag to the cookie, which makes it inaccessible to browser scripting languages such as JavaScript. session.cookie_httponly = ; Handler used to serialize data. php is the standard serializer of PHP. session.serialize_handler = php ; Define the probability that the 'garbage collection' process is started ; on every session initialization. ; The probability is calculated by using gc_probability/gc_divisor, ; e.g. 1/100 means there is a 1% chance that the GC process starts ; on each request. session.gc_probability = 1 session.gc_divisor = 1000 ; After this number of seconds, stored data will be seen as 'garbage' and ; cleaned up by the garbage collection process. session.gc_maxlifetime = 1440 ; NOTE: If you are using the subdirectory option for storing session files ; (see session.save_path above), then garbage collection does *not* ; happen automatically. You will need to do your own garbage ; collection through a shell script, cron entry, or some other method. ; For example, the following script would is the equivalent of ; setting session.gc_maxlifetime to 1440 (1440 seconds = 24 minutes): ; cd /path/to/sessions; find -cmin +24 | xargs rm ; PHP 4.2 and less have an undocumented feature/bug that allows you to ; to initialize a session variable in the global scope, albeit register_globals ; is disabled. PHP 4.3 and later will warn you, if this feature is used. ; You can disable the feature and the warning separately. At this time, ; the warning is only displayed, if bug_compat_42 is enabled. session.bug_compat_42 = 0 session.bug_compat_warn = 1 ; Check HTTP Referer to invalidate externally stored URLs containing ids. ; HTTP_REFERER has to contain this substring for the session to be ; considered as valid. session.referer_check = ; How many bytes to read from the file. session.entropy_length = 0 ; Specified here to create the session id. session.entropy_file = ;session.entropy_length = 16 ;session.entropy_file = /dev/urandom ; Set to {nocache,private,public,} to determine HTTP caching aspects ; or leave this empty to avoid sending anti-caching headers. session.cache_limiter = nocache ; Document expires after n minutes. session.cache_expire = 180 ; trans sid support is disabled by default. ; Use of trans sid may risk your users security. ; Use this option with caution. ; - User may send URL contains active session ID ; to other person via. email/irc/etc. ; - URL that contains active session ID may be stored ; in publically accessible computer. ; - User may access your site with the same session ID ; always using URL stored in browser's history or bookmarks. session.use_trans_sid = 0 ; Select a hash function ; 0: MD5 (128 bits) ; 1: SHA-1 (160 bits) session.hash_function = 0 ; Define how many bits are stored in each character when converting ; the binary hash data to something readable. ; ; 4 bits: 0-9, a-f ; 5 bits: 0-9, a-v ; 6 bits: 0-9, a-z, A-Z, "-", "," session.hash_bits_per_character = 5 ; The URL rewriter will look for URLs in a defined set of HTML tags. ; form/fieldset are special; if you include them here, the rewriter will ; add a hidden <input> field with the info which is otherwise appended ; to URLs. If you want XHTML conformity, remove the form entry. ; Note that all valid entries require a "=", even if no value follows. url_rewriter.tags = "a=href,area=href,frame=src,input=src,form=fakeentry" [MSSQL] ; Allow or prevent persistent links. mssql.allow_persistent = On ; Maximum number of persistent links. -1 means no limit. mssql.max_persistent = -1 ; Maximum number of links (persistent+non persistent). -1 means no limit. mssql.max_links = -1 ; Minimum error severity to display. mssql.min_error_severity = 10 ; Minimum message severity to display. mssql.min_message_severity = 10 ; Compatibility mode with old versions of PHP 3.0. mssql.compatability_mode = Off ; Connect timeout ;mssql.connect_timeout = 5 ; Query timeout ;mssql.timeout = 60 ; Valid range 0 - 2147483647. Default = 4096. ;mssql.textlimit = 4096 ; Valid range 0 - 2147483647. Default = 4096. ;mssql.textsize = 4096 ; Limits the number of records in each batch. 0 = all records in one batch. ;mssql.batchsize = 0 ; Specify how datetime and datetim4 columns are returned ; On => Returns data converted to SQL server settings ; Off => Returns values as YYYY-MM-DD hh:mm:ss ;mssql.datetimeconvert = On ; Use NT authentication when connecting to the server mssql.secure_connection = Off ; Specify max number of processes. -1 = library default ; msdlib defaults to 25 ; FreeTDS defaults to 4096 ;mssql.max_procs = -1 ; Specify client character set. ; If empty or not set the client charset from freetds.comf is used ; This is only used when compiled with FreeTDS ;mssql.charset = "ISO-8859-1" [Assertion] ; Assert(expr); active by default. ;assert.active = On ; Issue a PHP warning for each failed assertion. ;assert.warning = On ; Don't bail out by default. ;assert.bail = Off ; User-function to be called if an assertion fails. ;assert.callback = 0 ; Eval the expression with current error_reporting(). Set to true if you want ; error_reporting(0) around the eval(). ;assert.quiet_eval = 0 [COM] ; path to a file containing GUIDs, IIDs or filenames of files with TypeLibs ;com.typelib_file = ; allow Distributed-COM calls ;com.allow_dcom = true ; autoregister constants of a components typlib on com_load() ;com.autoregister_typelib = true ; register constants casesensitive ;com.autoregister_casesensitive = false ; show warnings on duplicate constant registrations ;com.autoregister_verbose = true [mbstring] ; language for internal character representation. ;mbstring.language = Japanese ; internal/script encoding. ; Some encoding cannot work as internal encoding. ; (e.g. SJIS, BIG5, ISO-2022-*) ;mbstring.internal_encoding = EUC-JP ; http input encoding. ;mbstring.http_input = auto ; http output encoding. mb_output_handler must be ; registered as output buffer to function ;mbstring.http_output = SJIS ; enable automatic encoding translation according to ; mbstring.internal_encoding setting. Input chars are ; converted to internal encoding by setting this to On. ; Note: Do _not_ use automatic encoding translation for ; portable libs/applications. ;mbstring.encoding_translation = Off ; automatic encoding detection order. ; auto means ;mbstring.detect_order = auto ; substitute_character used when character cannot be converted ; one from another ;mbstring.substitute_character = none; ; overload(replace) single byte functions by mbstring functions. ; mail(), ereg(), etc are overloaded by mb_send_mail(), mb_ereg(), ; etc. Possible values are 0,1,2,4 or combination of them. ; For example, 7 for overload everything. ; 0: No overload ; 1: Overload mail() function ; 2: Overload str*() functions ; 4: Overload ereg*() functions ;mbstring.func_overload = 0 ; enable strict encoding detection. ;mbstring.strict_detection = Off [FrontBase] ;fbsql.allow_persistent = On ;fbsql.autocommit = On ;fbsql.show_timestamp_decimals = Off ;fbsql.default_database = ;fbsql.default_database_password = ;fbsql.default_host = ;fbsql.default_password = ;fbsql.default_user = "_SYSTEM" ;fbsql.generate_warnings = Off ;fbsql.max_connections = 128 ;fbsql.max_links = 128 ;fbsql.max_persistent = -1 ;fbsql.max_results = 128 [gd] ; Tell the jpeg decode to libjpeg warnings and try to create ; a gd image. The warning will then be displayed as notices ; disabled by default ;gd.jpeg_ignore_warning = 0 [exif] ; Exif UNICODE user comments are handled as UCS-2BE/UCS-2LE and JIS as JIS. ; With mbstring support this will automatically be converted into the encoding ; given by corresponding encode setting. When empty mbstring.internal_encoding ; is used. For the decode settings you can distinguish between motorola and ; intel byte order. A decode setting cannot be empty. ;exif.encode_unicode = ISO-8859-15 ;exif.decode_unicode_motorola = UCS-2BE ;exif.decode_unicode_intel = UCS-2LE ;exif.encode_jis = ;exif.decode_jis_motorola = JIS ;exif.decode_jis_intel = JIS [Tidy] ; The path to a default tidy configuration file to use when using tidy ;tidy.default_config = /usr/local/lib/php/default.tcfg ; Should tidy clean and repair output automatically? ; WARNING: Do not use this option if you are generating non-html content ; such as dynamic images tidy.clean_output = Off [soap] ; Enables or disables WSDL caching feature. soap.wsdl_cache_enabled=1 ; Sets the directory name where SOAP extension will put cache files. soap.wsdl_cache_dir="/tmp" ; (time to live) Sets the number of second while cached file will be used ; instead of original one. soap.wsdl_cache_ttl=86400 ; Local Variables: ; tab-width: 4 ; End:

2) Open Notepad on your computer.

3) Paste the code into Notepad.

4) Save the file as php.ini

5) Replace the php.ini file in your C:\php folder with the php.ini file you just saved.

No additional configuration changes are needed for this file to work with your Apache Server. They have been done for you!

There are only a few options a home user may wish to change later if you intend to use PHP to send email.
Sending email with PHP would also require you to install a Mail Transport Agent.
How to modify the configuration settings in the php.ini file for use with a Mail Transport Agent, will be provided near the bottom of this page.
The other thing you may wish to do is change the Maximum size for HTTP File Uploads using PHP
I have already bumped the size the original php.ini gives you from 2Meg to 30Meg. and 30 files Max can be selected in 1 upload.
This should accommodate most users needs considering the size of mp3's photo's, and small videos.
The Upload Directory is the default temp Directory.

In order for the Extensions enabled in the php.ini to load with PHP at Start Up, your C:\php directory needs to be in the Windows Path.
In order to put C:\php in the Windows Path Statement, so that it will be in effect when Windows Starts do the following:

Highlight the following text below in bold, Right Click on it, and Click Copy:

;C:\Program Files\Apache Software Foundation\Apache2.2;C:\php

Click Start >> Control Panel >> System >> Advanced Settings >> Environment Variables

Under "System Variables" Scroll down to the Variable named "Path".

Click on "Path" to Highlight it, and Click "Edit".

Click in the box named "Variable Value" (you should see your cursor there, and the blue highlight should go away).

Press the "End" Key on your Keyboard.

Hold down the "Ctrl" (Control) Key on the Keyboard, and while still holding the "Ctrl" Key down, Press the "V" key once.

You should see ;C:\Program Files\Apache Software Foundation\Apache2.2;C:\php added to the end of the line of text in the box named "Variable Value".

Click "OK".

Re-Boot your Computer to insure the new Windows Paths will be loaded in the Windows Path.

Using the php.ini above, you will be able to enable additional optional Extensions, if you like, as well as install more features later.
There are already many of the most common Extensions enabled in the php.ini provided above.
Don't forget to Re-boot for the Windows Path to take effect!
Re-Booting your computer will also restart Apache, which will load PHP, and all the Extensions (once you overwrite the httpd.conf with the one provided below. We will get to that! Right now we just want the path loaded in Windows).
This will also happen when you re-start Apache, but not this time, because you need the httpd.conf provided below, before PHP will load in Apache.

Wimdows (Quality of Service Driver) QoS interrupts Apaches ability to Server Files, and also causes incomplete downloads.
Apache does not support the QoS extensions to the WinSock API.
To see if you are running QoS and disable it if necessary, do the following:

Be logged in as an administrator
Click Start and Select Run.
In the Run Box type or (copy and paste):

gpedit.msc

Click OK

When the "Group Policy Editor" opens, Expand "Computer Configuration".
Expand "Administrative Templates".
Expand "Network".
Double click "QoS Packet Scheduler" on the right.
Double click "Limit reservable bandwidth".
On the "Setting" Tab:
Click "Enabled".
Change to the Bandwidth limit from it's default of 20% to 0% to turn it off.
Click "OK"
Exit the Group Policy Editor, and Reboot your Computer for the changes to take effect.

Many of you may wish to send email from PHP, or scripts using your Apache Server.
You may already have pages, and scripts that uses the linux sendmail feature.
Many times these are purchased scripts, that are updated frequently, and editing them every time, for a different email sending solution is a hassle.
You need Sendmail in Windows!
This is what you need to add the sendmail function to PHP, for your Server running PHP in Windows:

Download the Sendmail Zip File Here!

Using your Zip File Extraction Utility, extract the sendmail.zip file to the Root of Drive C:
In other words extract right to Drive C
Do Not extract the contents to any folder, only extract to Drive C:
If you extracted sendmail.zip correctly, sendmail.zip will place a sendmail folder right in Drive C:
The path of the extracted sendmail folder will be this:  C:\sendmail
The preconfigured php.ini file provided above IS ALREADY CONFIGURED for Sendmail!
The only thing to do now is to configure sendmail to work with one of your email accounts.

Configuring The sendmail.ini file for your email service:

The configuration settings are identical to those used by an email client to access your email account.
I created a FREE Gmail Account for dedicated use with mine, but you can use any POP3 or IMAP accessible email account.
Configuration settings for FREE Gmail accounts is provided HERE for your convenience, or use the actual Gmail POP3 settings given below.
If you do use a FREE Gmail account, don't forget to enable POP3 and / or IMAP Access in
Gmail's "Mail Settings" under "Forwarding and POP/IMAP".

Open Notepad, and look in the sendmail folder for the sendmail.ini file.     C:\sendmail\sendmail.ini
Open the sendmail.ini file with Notepad.

Below I have a reference chart listing examples of the 3 possible sendmail.ini configurations:
Notice the use of semicolons in front of configuration settings.
Any line in the sendmail.ini beginning with a semicolon will be ignored / not used as a setting by sendmail.

smtp_ssl should be set to auto for SSLor TLS:    smtp_ssl=auto
If your mail server uses neither SSL or TLS then use:    smtp_ssl=none

For example, using the information provide by Gmail:

Your sendmail.ini configuration would contain this:

If you have problems, uncomment the lines error_logfile and debug_logfile so you can trace what went wrong.
Note: The Error Log and Debug Log files will be created in folder C:\sendmail

Test your sendmail function by making some php pages utilizing sendmail yourself, or try this easy to use online php contact form generator.

I suggest adding the sendmail directory to your path statement for some (not all) pesky scripts, which have a hard time with the path to sendmail, on
a Windows machine. This allows you to reduce the path in your scripts to just   sendmail   and gets around Linux / Windows path issues.

In order to put C:\sendmail in the Windows Path Statement, so that it will be in effect when Windows Starts do the following:

Highlight the following text below in bold, Right Click on it, and Click Copy:

;C:\sendmail

Click Start >> Control Panel >> System >> Advanced Settings >> Environment Variables

Under "System Variables" Scroll down to the Variable named "Path".

Click on "Path" to Highlight it, and Click "Edit".

Click in the box named "Variable Value" (you should see your cursor there, and the blue highlight should go away).

Press the "End" Key on your Keyboard.

Hold down the "Ctrl" (Control) Key on the Keyboard, and while still holding the "Ctrl" Key down, Press the "V" key once.

You should see ;C:\Program Files\Apache Software Foundation\Apache2.2;C:\php added to the end of the line of text in the box named "Variable Value".

Click "OK".

Re-Boot your Computer to insure the new Windows Paths will be loaded in the Windows Path.

Basic Information

The Apache Configuration File is called httpd.conf
Open up your httpd.conf file with Notepad, or even better, download a FREE text editor that indicates line numbers Here.
Line numbers are handy if you get an Error, because the Error message will tell you what line the error is on.
Notepad wont show you the line numbers. Notepad++ will!
Apache's configuration file is a text file named httpd.conf
The httpd.conf file is located here:
C:/Program Files/Apache Software Foundation/Apache2.2/conf
Note the conf (short for configuration) file is in Apache's "conf "directory.

Once the httpd.conf file is open, you will notice allot of text with # as the first character of each line.
The # is used to make comments, and is not actual configuration information that Apache uses.
Apache ignores the contents of any line beginning with a #.
Help information after a # is there for your benefit and is meant as a reminder.
The # is also handy to temporarily remove actual configuration information from the configuration until it is needed later.

Since Apache will ignore information after the #, configuration information for many features / modules that installed with Apache, but are not in use, are included in the default httpd.conf for your convenience. They are simply disabled by the addition of the #.
Should you desire to use them, you simply remove the #, then save the edited httpd.conf, and restart Apache for the changes to take effect.
You are not editing right now, so there is no need to save, or restart yet!

DO NOT remove the # from in front of everything, or even in front of all of the modules!!! You don't want all of the modules!!!
If you remove the # from in front of help information, you will create errors that will most likely crash Apache Server.
There may be additional configuration needed before you can run some of the modules with the # disabling them from loading when Apache starts.

Note: The slashes used in path statements in configuration files related to Apache and PHP may vary from the slashes in path statements for the SAME path in Windows. This may seem confusing, but it is normal. Paths in Apache or PHP are relative to a Unix / Linux environment, even though you are in running them in a Windows environment. If you see a path that appears to use the wrong slash, forward / for back \, or back \ for forward /, do not always assume it is wrong.  Likewise, if you are editing something, and have a path issue, do not always assume the slash is correct.

You have the option to use the Pre-Configured httpd.conf and php.ini files provided on this page, or you may follow the Step by Step procedure below the section, using the Pre-Configured file, to further customize the httpd.conf  file to suite your desired configuration needs.

This is more than the httpd.conf that is provided when Apache Server is installed.
It has many of the most desirable configurations already done to it, including added code to integrate PHP into Apache Server, enabling the rewrite module, and giving your directory listings the best look, as well as automatically indexing, and resizing columns so that your file names wont be truncated, making sure folders are listed first, enabling the use of .htaccess files to customize and password protect your web directories / web folders, in addition files beginning with .ht will remain hidden from visitors, as well as the thumbs.db files that Windows automatically adds to any folders containing media. There are really only a few options that you may want to change to thoroughly enjoy the use of this configuration, and they are listed and explained directly below in this very section of the Installation instructions. They are IP Address, Port, the DocumentRoot, and the Server Administrators email address. If you wish to change any of these 4 things, instructions will be provided below.

To use this preconfigured httpd.conf code:

1) Highlight and Copy all the Code in the box directly below.

httpd.conf

# # This is the main Apache HTTP server configuration file. It contains the # configuration directives that give the server its instructions. # See <URL:http://httpd.apache.org/docs/2.2> for detailed information. # In particular, see # <URL:http://httpd.apache.org/docs/2.2/mod/directives.html> # 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 httpd.exe is located # will be used by default. It is recommended that you always supply # an explicit drive letter in absolute paths to avoid confusion. # # 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. # # Listen 12.34.56.78:80 Listen 192.168.0.10:80 # # Timeout: The number of seconds before receives and sends time out. # Timeout 150 # # KeepAlive HTTP/1.1 persistent connection feature, provides long-lived HTTP sessions, which allow multiple requests to be sent over the same TCP connection. # Results in an almost 50% speedup in latency times for HTML documents and with many images. KeepAlive On KeepAliveTimeout 10 MaxKeepAliveRequests 128 # # UseCanonicalName: Determines how Apache constructs self-referencing # URLs and the SERVER_NAME and SERVER_PORT variables. # When set "Off", Apache will use the Hostname and Port supplied # by the client. When set "On", Apache will use the value of the # ServerName directive. # UseCanonicalName Off # # AccessFileName: The name of the file to look for in each directory # for additional configuration directives. See also the AllowOverride # directive. # # AccessFileName .htaccess # # HostnameLookups: Log the names of clients or just their IP addresses # e.g., www.apache.org (on) or 204.62.129.132 (off). # The default is off because it'd be overall better for the net if people # had to knowingly turn this feature on, since enabling it means that # each client request will result in AT LEAST one lookup request to the # nameserver. # # HostnameLookups Off # # SendBufferSize: The server will set the TCP Send Buffer Size to the number of bytes specified. # If set to a value of 0 the server will use the operating system default - SendBufferSize 0 # SendBufferSize 1492 # # 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_alias_module modules/mod_authn_alias.so #LoadModule authn_anon_module modules/mod_authn_anon.so #LoadModule authn_dbd_module modules/mod_authn_dbd.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 authnz_ldap_module modules/mod_authnz_ldap.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_owner_module modules/mod_authz_owner.so LoadModule authz_user_module modules/mod_authz_user.so LoadModule autoindex_module modules/mod_autoindex.so #LoadModule cache_module modules/mod_cache.so #LoadModule cern_meta_module modules/mod_cern_meta.so LoadModule cgi_module modules/mod_cgi.so #LoadModule charset_lite_module modules/mod_charset_lite.so #LoadModule dav_module modules/mod_dav.so #LoadModule dav_fs_module modules/mod_dav_fs.so #LoadModule dav_lock_module modules/mod_dav_lock.so #LoadModule dbd_module modules/mod_dbd.so LoadModule deflate_module modules/mod_deflate.so LoadModule dir_module modules/mod_dir.so #LoadModule disk_cache_module modules/mod_disk_cache.so #LoadModule dumpio_module modules/mod_dumpio.so LoadModule env_module modules/mod_env.so LoadModule expires_module modules/mod_expires.so #LoadModule ext_filter_module modules/mod_ext_filter.so #LoadModule file_cache_module modules/mod_file_cache.so #LoadModule filter_module modules/mod_filter.so LoadModule headers_module modules/mod_headers.so #LoadModule ident_module modules/mod_ident.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 ldap_module modules/mod_ldap.so #LoadModule logio_module modules/mod_logio.so LoadModule log_config_module modules/mod_log_config.so #LoadModule log_forensic_module modules/mod_log_forensic.so #LoadModule mem_cache_module modules/mod_mem_cache.so LoadModule mime_module modules/mod_mime.so LoadModule mime_magic_module modules/mod_mime_magic.so LoadModule negotiation_module modules/mod_negotiation.so LoadModule php5_module "c:/php/php5apache2_2.dll" #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_ftp_module modules/mod_proxy_ftp.so #LoadModule proxy_http_module modules/mod_proxy_http.so #LoadModule proxy_scgi_module modules/mod_proxy_scgi.so #LoadModule reqtimeout_module modules/mod_reqtimeout.so LoadModule rewrite_module modules/mod_rewrite.so LoadModule setenvif_module modules/mod_setenvif.so #LoadModule speling_module modules/mod_speling.so #LoadModule ssl_module modules/mod_ssl.so #LoadModule status_module modules/mod_status.so #LoadModule substitute_module modules/mod_substitute.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 version_module modules/mod_version.so #LoadModule vhost_alias_module modules/mod_vhost_alias.so <IfModule !mpm_netware_module> <IfModule !mpm_winnt_module> # # If you wish httpd to run as a different user or group, you must run # httpd as root initially and it will switch. # # User/Group: The name (or #number) of the user/group to run httpd as. # It is usually good practice to create a dedicated user and group for # running httpd, as with most system services. # User daemon Group daemon </IfModule> </IfModule> # '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 # ServerAdmin admin@mydomain.com # ServerTokens controls whether the Server description at the bottom of directory lists is sent back to clients # including information about the Server, its version, the OS-type, and information about compiled-in modules like PHP. # It may become desirable to limit this information, for security purposes. # http://httpd.apache.org/docs/2.1/mod/core.html#servertokens # ServerTokens Major|Minor|Min|Prod|OS|Full # Default: ServerTokens Full ServerTokens Full # # 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 internet IP address here. # for ssl certificates this must now match the INTERNET IP address or the domain name used # in your Certificate, unless this is being used exclusively on an intranet. # # # ServerName 192.168.0.10:80 ServerName 72.168.195.50 # # 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:/www" # # 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 allow,deny Deny from 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:/www"> # # 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 # http://httpd.apache.org/docs/2.2/mod/core.html#options # for more information. # Options Indexes IncludesNOEXEC FollowSymLinks ExecCGI MultiViews IndexOptions FancyIndexing IndexOptions FoldersFirst IndexOptions NameWidth=* IndexOptions DescriptionWidth=* IndexOptions SuppressHTMLPreamble IndexOptions IconsAreLinks IndexIgnore Thumbs.db # # IndexStyleSheet "C:/www/css/style.css" # # 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 All # Controls who can get stuff from this server. # # Sets up User Agent List that can be Blocked # BrowserMatchNoCase - UA # SetEnvIf Request_Protocol "HTTP/1.0" UA # SetEnvIfNoCase Request_URI ".*w00tw00t.*" UA # SetEnvIf Request_Method "HEAD" UA # SetEnvIfNoCase User-Agent "BadUA" UA # SetEnvIfNoCase User-Agent "Mozilla/4.0" UA # NoCase Makes SetEnvIf Case-insensitive. # Allow only if HOST Header is Present in Request: SetEnvIfNoCase Host .+ UA # SetEnvIf User-Agent "^$" UA SetEnvIf User-Agent "^_" UA SetEnvIf User-Agent "^-" UA SetEnvIfNoCase User-Agent "ZmEu" UA SetEnvIfNoCase User-Agent "Python-urllib" UA SetEnvIfNoCase User-Agent "Morfeus" UA SetEnvIfNoCase User-Agent "MSIE 5.5" UA SetEnvIfNoCase User-Agent "MSIE 6.0" UA SetEnvIfNoCase User-Agent "Windows 98" UA SetEnvIfNoCase User-Agent "Firefox/3" UA SetEnvIfNoCase User-Agent "Chrome/13" UA # SetEnvIfNoCase User-Agent "facebookexternalhit" UA # Make an exception to deliver a custom error page # without creating another error. # Make exceptions for your stylesheet, and favicon # so your custom 403 Error Page can use them. # SetEnvif Request_URI "^/(style\.css|favicon\.ico|403\.php)$" !UA SetEnvif Request_URI "403.php" !UA SetEnvif Request_URI "403.htm" !UA SetEnvif Request_URI "style.css" !UA SetEnvif Request_URI "favicon.ico" !UA # # Defines the Allow and Block Rules Order allow,deny Allow from all Deny from env=UA # Deny from 31.210.20.17 # # Compress Content sent by up to 75% # Requires: deflate_module modules/mod_deflate.so above to be loaded. # Remove Hash from line below to compress those file types that are safe to compress, for all Browsers. # AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css image/x-icon image/bmp AddOutputFilterByType DEFLATE text/html AddOutputFilterByType DEFLATE text/plain AddOutputFilterByType DEFLATE text/xml AddOutputFilterByType DEFLATE text/css AddOutputFilterByType DEFLATE text/csv AddOutputFilterByType DEFLATE image/x-icon AddOutputFilterByType DEFLATE image/bmp AddOutputFilterByType DEFLATE application/xml AddOutputFilterByType DEFLATE application/xhtml+xml AddOutputFilterByType DEFLATE application/rss+xml AddOutputFilterByType DEFLATE application/javascript AddOutputFilterByType DEFLATE application/x-javascript SetEnvIfNoCase Request_URI \.(?:gif|jpe?g|png)$ no-gzip dont-vary SetEnvIfNoCase Request_URI \.pdf$ no-gzip dont-vary SetEnvIfNoCase Request_URI \.(?:mpe?g|avi|mp4|mov|rm|asf|flv|swf)$ no-gzip dont-vary SetEnvIfNoCase Request_URI \.(?:mp3|wav|m4a)$ no-gzip dont-vary SetEnvIfNoCase Request_URI \.(?:zip|rar|7z|tar|t?gz)$ no-gzip dont-vary # # Turn on Expires and set default to 0 ExpiresActive On ExpiresDefault A0 # Set up caching on media files for 1 year (forever?) <FilesMatch "\.(flv|ico|pdf|avi|mov|mpg|mp4|m4a|m4p|ppt|doc|mp3|swf|wmv|wav|zip|iso)$"> ExpiresDefault A29030400 Header append Cache-Control "public" </FilesMatch> # Set up caching on media files for 1 week <FilesMatch "\.(gif|jpg|jpeg|png|swf)$"> ExpiresDefault A604800 Header append Cache-Control "public" </FilesMatch> # Set up 1 Day caching on commonly updated files <FilesMatch "\.(xml|txt|html|htm|js|css)$"> ExpiresDefault A86400 Header append Cache-Control "proxy-revalidate" </FilesMatch> # Force no caching for dynamic files <FilesMatch "\.(php|cgi|pl)$"> ExpiresActive Off Header set Cache-Control "private, no-cache, no-store, proxy-revalidate, no-transform" Header set Pragma "no-cache" </FilesMatch> # # File Descriptions for use in Directory Index # AddDescription "Archive Disk Image File" .iso AddDescription "Archive RAR File" .rar AddDescription "Archive Zip File" .zip .7zip AddDescription "Archive File" .tar .Z .z .tgz .gz AddDescription "Audio File MP3" .mp3 AddDescription "Audio File M4a MPEG 4 Audio" .m4a AddDescription "Audio File M4p AAC Audio - Apple iTunes" .m4p AddDescription "Audio File WAV Format" .wav AddDescription "Audio File Midi Format" .mid AddDescription "Batch Processing File" .bat AddDescription "Blackberry Backup File" .ipd AddDescription "Cascading Style Sheet File" .css AddDescription "Compiled HTML Help File" .chm AddDescription "DOS Command File" .com AddDescription "Dynamic Link Library File" .dll AddDescription "Email Message File" .eml AddDescription "Executable File" .exe AddDescription "Windows Shortcut File" .lnk AddDescription "Executable File Windows Installer" .msi AddDescription "Extensible Markup Language File" .xml AddDescription "Garmin GPS Database File" .gdb AddDescription "Hypertext Meta Language File" .htm .html .shtml AddDescription "Hypertext Preprocessor File" .php AddDescription "Icon File" .ico AddDescription "Image File BMP" .bmp AddDescription "Image File Gif" .gif AddDescription "Image File Gimp" .xcf AddDescription "Image File JPG" .jpg .jpeg AddDescription "Image File PNG" .png AddDescription "Image File Photoshop Image" .psd AddDescription "Image File Cannon RAW Image Format" .RAW .raw AddDescription "Image File Fuji RAW Image Format" .RAF .raf AddDescription "Image File TIFF" .tif AddDescription "Information File" .inf AddDescription "Java Script Source Code" .js AddDescription "KeePass Database File" .kdb AddDescription "Microsoft Office Access Database File" .mdb AddDescription "Microsoft Office Word Document File" .doc .docx AddDescription "Microsoft Office Outlook Backup File" .pst AddDescription "Microsoft Office Powerpoint Presentation File" .ppt .pptx AddDescription "Microsoft Office Powerpoint Slide Show File" .pps AddDescription "Microsoft Office Publisher File" .pub AddDescription "Microsoft Office Excel Spreadsheet File" .xls .xlsx AddDescription "Microsoft Office Visio File" .vsd AddDescription "Microsoft Windows Address Book File" .wab .WAB AddDescription "Portable Document Format - Adobe Reader File" .pdf AddDescription "Registry Data File" .reg AddDescription "Remote Desktop Connection Configuration File" .rdp AddDescription "Rich Text Format Document File" .rtf AddDescription "Screen Saver File Windows" .scr AddDescription "System File" .sys AddDescription "Text File" .txt AddDescription "Internet Shortcut" .url AddDescription "Visual Basic Script File" .vbs AddDescription "Video File 3GP" .3gp AddDescription "Video File AVI Format" .avi .divx AddDescription "Video File Flash Format" .flv AddDescription "Video File Shockwave Flash Format" .swf AddDescription "Video File - Apple iTunes Video" .m4v AddDescription "Video File MOV Format Apple Quicktime" .mov .qtm AddDescription "Video File MPEG" .mpg .mpeg AddDescription "Video File MPEG-4" .mp4 .mp4v AddDescription "Video File MPEG DVD" .vob AddDescription "Video File Real Player" .rm .rmd .rv AddDescription "Video File Windows Media" .wmv .wm AddDescription "Video File Xvid Format" .xvid # </Directory> # # # # Remove the hash in front of the <IfModule rewrite_module> section # below and edit RewriteCond and RewriteRule to Add rewrite rules # See logging section below for troubleshooting rewrite rules # #<IfModule rewrite_module> # Options FollowSymlinks # RewriteEngine on # RewriteCond %{HTTP_REFERER} ^$ [OR] # RewriteCond %{HTTP_USER_AGENT} "bad useragent" [NC] # RewriteRule .* - [F] #</IfModule> # # # # Remove the hash in front of the <IfModule rewrite_module> section # below and edit RewriteCond and RewriteRule to Add rewrite rules # See logging section below for troubleshooting rewrite rules # #<IfModule rewrite_module> # Options FollowSymlinks # RewriteEngine on # RewriteCond %{HTTP_REFERER} ^$ [OR] # RewriteCond %{HTTP_USER_AGENT} "bad useragent" [NC] # RewriteRule .* - [F] #</IfModule> # # # DirectoryIndex: sets the file that Apache will serve if a directory # is requested. # # UserDir enabled # UserDir disabled root # UserDir /cgi # <IfModule dir_module> DirectoryIndex index.html index.htm index.php </IfModule> # # The following lines prevent .htaccess and .htpasswd files from being # viewed by Web clients. # <FilesMatch "^\.ht"> Order allow,deny Deny from all Satisfy 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 \"%{Referer}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 \"%{Referer}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 # # Error Log for Troubleshooting Rewrite Rules: # If you get the following error: # Request exceeded the limit of 10 internal redirects due to probable configuration error. # Use 'LimitInternalRecursion' to increase the limit if necessary. # Use 'LogLevel debug' to get a backtrace. # To debugging Rewrite module errors remove the hash # from RewriteLogLevel 3, and RewriteLog "logs/rewrite.log" # RewriteLogLevel 3 # RewriteLog "logs/rewrite.log" # </IfModule> <IfModule status_module> # # Allow server status reports generated by mod_status, # with the URL of http://servername/server-status # Change the ".example.com" to match your domain to enable. # ExtendedStatus On <Location /server-status> SetHandler server-status Order deny,allow Deny from all Allow from 192.168.0.10 </Location> </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:/cgi-bin/" # ScriptAlias /cgi-bin/ "C:/Program Files/Apache Software Foundation/Apache2.2/cgi-bin/" </IfModule> <IfModule cgid_module> # # ScriptSock: On threaded servers, designate the path to the UNIX # socket used to communicate with the CGI daemon of mod_cgid. # #Scriptsock logs/cgisock </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/"> <Directory "C:/cgi-bin/"> # AllowOverride All # Options Indexes FollowSymLinks ExecCGI MultiViews AllowOverride None Options None Order allow,deny Allow from all </Directory> # # 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 Addtype application/x-pdf .pdf # # 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 .pl # This causes all .htm and .html files to be searched for server-side include tags - bad for .php. AddHandler server-parsed .htm .html # 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 # AddType application/x-httpd-php .php AddType application/x-httpd-php .phtml # </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 # #ErrorDocument 400 /error/400.php #ErrorDocument 401 /error/401.php #ErrorDocument 403 /error/403.php #ErrorDocument 404 /error/404.php #ErrorDocument 500 /error/500.htm # # # 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 # # # AcceptEx() is a Microsoft WinSock v2 API that provides some performance improvements over the use of the BSD style accept() API in certain circumstances. # Some popular Windows products, typically virus scanning or virtual private network packages, have bugs that interfere with the proper operation of AcceptEx() # Use this directive to disable the use of AcceptEx() Win32DisableAcceptEx # # # 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 # Add a line to the bottom of Server Generated Pages with the Apache Version ServerSignature on # Secure (SSL/TLS) connections # Include conf/extra/httpd-ssl.conf #SSLSessionCache "shmcb:C:\Program Files\Apache Software Foundation\Apache2.2\logs\ssl_gcache_data(512000)" # # 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 Include conf/extra/httpd-ssl.conf </IfModule> # # Path to the directory containing the PHP.ini File # PHPIniDir "C:/php" #

2) Open Notepad on your computer.

3) Paste the code into Notepad.

4)  Edit any changes you desire to the IP Address, Port Number, Document Root, and email address as described below, using the simple instructions provided below, titled "Editing The Pre-Configured httpd.conf for Apache and PHP file".

5) If you did not change anything using the instructions below, just Save the file as httpd.conf  in the following location:
C:\Program Files\Apache Software Foundation\Apache2.2\conf
Overwrite the file that is there.
Apache creates a backup of the original httpd.conf file, in case you mess things up really badly.
The backup original of the original file is located in the C:\Program Files\Apache Software Foundation\Apache2.2\conf\original  folder.

6) Create the Document Root Folder on your Hard Drive. The un-edited httpd.conf given to you above is pre-configured to use C:\www as the Document Root. If you changed it using the instructions below, then use the path you configured the httpd.conf DocumentRoot for.

7) Test your httpd.conf file, by following these instructions :

Testing Configuration Changes, before you attempt to start Apache with them:

If you have made changes to your httpd.conf file, and saved them, you will want to test them prior to Starting Apache with them.
To test your configuration changes, the httpd.conf must be located in the C:\Program Files\Apache Software Foundation\Apache2.2\conf folder.
This means you MUST overwrite the file that is there before the test utility will be able to check it.
Apache creates a backup of the original httpd.conf file, in case you mess things up really badly.
The backup original of the original file is located in the C:\Program Files\Apache Software Foundation\Apache2.2\conf\original  folder.
To Test your new configuration before attempting to Starting Apache do the following:

Click Start >> All Programs >> Apache HTTP Server 2.2 >> Configure Apache Server >> Test Configuration.

If a Window pops up, quickly, saying OK, and closes instantly, your configuration has no errors.
If you made a mistake, it will open a window telling you there is an Error on Line X, where X represents a line number, and there will be a count down, until the window closes.
If there is an Error, you will want a text editor that indicates line numbers, especially if you made changes to more than 1 line.
You can get a FREE text editor that indicates line numbers, and is appropriate for this purpose HERE.

8) Be sure you have installed PHP and replaced the php.ini with the one provided as per the PHP installation instructions listed above.
This httpd.conf file is already configured to run PHP on your installation of Apache Server.
Once Apache and PHP are installed on your computer as described above, and your httpd.conf has the configuration you desire, and you have overwritten the original httpd.conf file with the configured httpd.conf file, and it tests OK, you are ready to try it.
In order for your configuration to take effect, you must Stop Apache.
After Apache Stops, Start Apache again, so that it can load the new configuration settings.

9)Test your Installation.

Create the test file using the instructions in the box below named Testing PHP, and place the file in your DocumentRoot Folder.
Type your http://192.168.0.10 or whatever IP Address you changed the DocumentRoot to, and press Enter on your keyboard.

Your Web Browser should be displaying the contents of your DocumentRoot Folder, with the test.php in it.
Do not be alarmed that it did not open the test.php file, the Server is configured to open index.htm and index.html and index.php files when ever a browser lands there, not test.php.
If you had an index.htm or index.html or index.php file there it would have displayed that page, instead of the folder contents.
Click on your test.php file to run it, and open its results in your browser.

You should see a PHP test page with allot of information.
If you see the PHP test page, Congratulations!!!
Not only is your server working correctly, but PHP is also functioning correctly.

IP Address:
This copy and paste httpd.conf file below is set up for a computer with an IP Address of 192.168.0.10
There are 2 places in this configuration, where the IP Address is specified, and must be changed, if you wish to use a different IP Address than 192.168.0.10
Those lines in the httpd.conf configuration file are:

Listen 192.168.0.10:80

ServerName 192.168.0.10:80

The :80 at the end of the IP Address is the Port Number
192.168.0.10:80 indicates an IP Address of 192.168.0.10 on Port 80
There is a Colon separating the IP Address and the Port number. There are no spaces used between the IP Address and Port Number.
There is 1 space used between Listen and its IP Address, and 1 space used between ServerName and its IP Address.
You can change the IP Address and Port number by editing those 2 lines, but the IP Address and Port Number must be identical to one another on those 2 lines when you save the httpd.conf file. In other words any changes made to the IP Address or Port Number of Listen, must also be made to the IP Address or Port Number of ServerName.

Port:
The Port is set to 80 in this configuration. Port 80 is the default of web browsers. If you wish to use a different port, you must edit this file in one place. To change the Port, look for this:
Listen 192.168.0.10:80
Change the 80, at the end of this IP Address to the different port you desire.
Notice it is separated by a Colon, not a dot, like the rest of the IP Address.

There are 2 places in this configuration, where the Port Number is specified, and must be changed, if you wish to use a different Port Number than 80
Those lines in the httpd.conf configuration file are:

Listen 192.168.0.10:80

ServerName 192.168.0.10:80

The :80 at the end of the IP Address is the Port Number.
192.168.0.10:80 indicates Port 80 with  an IP Address of 192.168.0.10
There is a Colon separating the IP Address and the Port number. There are no spaces used between the IP Address and Port Number.
There is 1 space used between Listen and its IP Address, and 1 space used between ServerName and its IP Address.
You can change the IP Address and Port number by editing those 2 lines, but the IP Address and Port Number must be identical to one another on those 2 lines when you save the httpd.conf file. In other words any changes made to the IP Address or Port Number of Listen, must also be made to the IP Address or Port Number of ServerName.

DocumentRoot:
The Document Root is the Root location of the Files your server will host.
Files and directories placed in the Folder on your Hard Drive, designated as the Document Root will be viewable to any Web Browser that visits your computers IP Address.
This httpd.conf specifies C:\www as the Folder / Directory on your Hard Drive that will contain the files the Server will display to any Web Browser visiting your computers IP Address.
To Use this as your httpd.conf file, you MUST create a C:\www directory on your Drive C: before overwriting the original httpd.conf and restarting Apache. Note: The www is in lower case!
To use a different folder on your Hard Drive, or on another Drive on your computer as the Document Root, you must edit 2 lines in the httpd.conf file.
Those 2 lines in the httpd.conf configuration file are:

DocumentRoot "C:/www"

<Directory "C:/www">

The Directory (folder) path is contained in quotes.
There are no spaces between the quotes and the specified path.
C:/ represents Drive C on the computer
www represents the folder (directory).
Notice this uses a forward slash in the path and not a back slash.
When you create the folder on your hard drive, the path in Windows is indicated with a back slash.
When you enter the path in the httpd.conf, the path uses forward slashes.

Email Address:
There may come a time when you wish to edit the email address of the Server Administrator, indicated by your Server.
This is done in the httpd.conf file on one line.
The lines in the httpd.conf configuration file is:

ServerAdmin admin@mydomain.com

admin@mydomain.com is the default email address indicated by the httpd.conf configuration file.
There is a single space between ServerAdmin and the desired email address of your choice.
Just replace admin@mydomain.com with the email address you prefer, and save the httpd.conf file.

cgi-bin
The Copy and Paste  httpd.conf  is set up to use a C:\cgi-bin Folder on your Server.
This path will not be hosted by the server, and directly available to outsiders,
so it is secure from hackers being able to drop malicious scripts in your servers cgi-bin directory, and execute them.
It is also easy for you to access, when you are developing your own scripts for your server.
To use this preconfigured directory, create a C:\cgi-bin directory on your Computer.
Open Windows Explorer and Browse to drive C:\ (the Root of drive C)
Right Click on the Right hand side of Windows Explorer, and go to "New",
then from the menu that pops out, Left Click on "Folder".
Type "cgi-bin" without the quotes, and press "Enter on your keyboard".

If you do not wish to use the  C"/cgi-bin  directory, you may edit the httpd.conf file.
To edit the cgi-bin path in the httpd.conf file, open the httpd.conf file in Notepad, or your favorite text editor.
Scroll down and look for:

ScriptAlias /cgi-bin/ "C:/cgi-bin/"
Edit the C"/cgi-bin path to the Windows Path that you desire.

NextScroll down and look for:

<Directory "C:/cgi-bin/">
Edit the C"/cgi-bin path in  <Directory "C:/cgi-bin/">  to match the path you chose in ScriptAlias /cgi-bin/ "C:/cgi-bin/" above.
 

Testing Configuration Changes, before you attempt to start Apache with them:

If you have made changes to your httpd.conf file, and saved them, you will want to test them prior to Starting Apache with them.
To test your configuration changes, the httpd.conf must be located in the C:\Program Files\Apache Software Foundation\Apache2.2\conf folder.
This means you MUST overwrite the file that is there before the test utility will be able to check it.
You can back up that file by copying it to another location if you like.
To Test your new configuration before attempting to Starting Apache do the following:

Click Start >> All Programs >> Apache HTTP Server 2.2 >> Configure Apache Server >> Test Configuration.

If a Window pops up, quickly, saying OK, and closes instantly, your configuration has no errors.
If you made a mistake, it will open a window telling you there is an Error on Line X, where X represents a line number, and there will be a count down, until the window closes.
If there is an Error, you will want a text editor that indicates line numbers, especially if you made changes to more than 1 line.
You can get a FREE text editor that indicates line numbers, and is appropriate for this purpose HERE.

If this is a first time edit of the httpd.conf file, done as part of the installation process in step 4 of "Pre-Configured httpd.conf for Apache and PHP", then return to "Pre-Configured httpd.conf for Apache and PHP" directly above this section, and continue on step 5 of the instructions now.
If you have been running this installation for a while, and have returned to make some changes, then restart Apache, and Enjoy!!!

To get access to your Apache Server from the Internet, once you have it set up and functioning, you will first need to set up Port Forwarding on your Router. You will need to access your Routers Configuration Settings, and find Port Forwarding.
Once you find Port Forwarding in your Routers Settings, set it to forward Port 80 (or the port you changed the httpd.conf to use) to your servers IP Address. Save those new settings in your Routers configuration.
Once that is done, any web browser that goes to your internet IP Address (NOT YOUR LOCAL NETWORK ADDRESS) will be forwarded to the Servers local network IP Address (The one you specified in the Port Forwarding settings in your Router).
Your internet address is the IP Address your Internet Service provider gives you when you log on.
The status page of your Router should tell you what your IP Address is on the internet.
As long as you are logged on with that internet IP Address, your friends and family will be able to point their Web Browsers at your Internet IP Address, and see what you have for them on your Apache Server.
If your Internet Service Provider always logs you on at the same IP Address (they give you a static IP Address), your server will always be right there. If your Internet IP Address changes, it should at least be the same as long as you are logged on.
Many people have service that is always on, and you can keep the same IP Address for a good amount of time.
This may be adequate for some people's occasional needs.
Other people will either need to get a static IP Address from their Internet Service Provider, or sign up for a forwarding service, that tracks your Internet IP Address changes, and provides you with a stable address that is always forwarded to whatever Internet IP address you currently have.
Many newer Routers have settings for these Services already built into them, that you can take advantage of.
Check your router for these settings, and you will find the names of some of these popular services already configured into it.

There is a simple way to password protect folders in your Apache Server Hosted Directory.
You will need to create a .htaccess file, and place it in the folders you wish to password protect.
Make sure you include the dot (.) at the beginning of the file name.

Creating an .htaccess file:
You can copy and paste the following into Notepad.
Edit the AuthName (If you desire), and AuthUserFile (to point to the path and filename you wish to store your User Names and Passwords in, then save the file as .htaccess in every directory/folder you wish to protect with those User Names and Passwords:

AuthName "Log In"
AuthType Basic
AuthUserFile C:\passwords\.htpasswd
require valid-user

AuthName is the Message the User Name and Password "Window" will display when asking users to log in.
AuthUserFile is the line with the path to the file that stores the usernames and encrypted passwords, that will be used for access to the folder you wish to password protect. The file does not have to be named .htpasswd, as in this example, but the .htaccess file in the folder you wish to password protect must point to it, and name it correctly. .htaccess can not be renamed. Apache looks for that specific file name.
For the sake of this guide, we will stick with the .htpasswd file name and the C:\passwords directory for it's location.
Notepad in Windows does not allow you to name the file .htaccess, and insists on naming it .htaccess.txt don't panic.
When you save the file in notepad, just put .htaccess in quotes ".htaccess" when saving it, and it will save it as .htaccess with no problem.
Use Windows Explorer to create a "passwords" folder on drive C:  ( C:\passwords ).
Open a Command Prompt window, and use the cd (change directory) command, to change directories to c:\passwords
By default command prompt should open on drive C: in your user folder.
If you are not on drive C:\  just type   C:   and press "Enter", to change drive letters to drive C:\.
Type   cd\   to return to the root of drive C:
At the C:\> prompt Type   cd passwords    to change to the   C:\passwords   folder you created.
Save the file with Notepad in the C:\passwords folder naming the file .htaccess using quotes ".htaccess"
If you can not name the file .htaccess for some reason, allow it to be named .htaccess.txt then using Command Prompt in the C:\passwords directory type:

ren .htaccess.txt .htaccess

and press "Enter".
ren is the command to rename a file. Your file is now named .htaccess
You can type dir to see the contents of the directory, and confirm the name of the file is now .htaccess
dir is the directory command, and it lists what is in the directory.
Since this is the first file in C:\passwords .htaccess should be easy to spot.
Next we will want to create our User Name and Password List (.htpasswd) file:

Creating the .htpasswd file:

The .htpasswd file contains the list of user names, and encrypted passwords to be used with your .htaccess file.
It is a good idea to keep the .htpasswd file in a folder that is NOT being hosted by Apache Server.

Go to the C:\Program Files\Apache Software Foundation\Apache2.2\bin  Folder on your computer, and copy the file named "htpasswd.exe" to your C:\WINDOWS Folder. This will insure that it is always in the path on your Windows computer. Now whenever you run htpasswd from a  command prompt, you can run it by simply typing htpasswd. Copying this file to WINDOWS only has to be done once!

Use Windows Explorer to create a "passwords" folder on drive C:  ( C:\passwords ) if you have not done so already.

Open a Command Prompt window, and use the cd (change directory) command,
to change directories to the one you wish  htpasswd to create your new .htpasswd file in ( c:\passwords ).

By default command prompt should open on drive C: in your user folder.
If you are not on drive C:\  just type   C:   and press "EnType   cd\   to return to the root of drive C:
At the C:\> prompt Type   cd passwords    to change to the   C:\passwords   folder.

Now we create a user name and password file!="left"> Now we create Place the User Name you wish to add to your user name and password list, on the end of the following command line, in place of "UserName" (without quotes), then enter the desired password when prompted.
To create a NEW .htpasswd file in the C:\passwords directory, where none exists use the -c option (create new, where Copy and Paste the following to "Terminal" at the prompt, and backspace/edit UserName (.htpasswd can also be edited/changed if you desire a different file name for your password list, but .htaccess must designate the same file name - handy if you have different access lists, for different directories. Always start the file name with .ht so that it will be hidden from visiting web browsers by Apache!)

htpasswd -c .htpasswd UserName

For examplewd -c .htpasswd UserName

htpasswd -c .htpasswd scott

Syntax: htpasswd optionalswitch path&filename username

Adding log ins to the .htpasswd file:

To ADD an additional login to an existing .htpasswd file open command prompt in the directory the .htpasswd file is in that you wish to add logins to.
Copy and Paste the following to command prompt at the cursor, and backspace/edit UserName
.htpasswd can also be a different .ht file name you created using the "Create New" procedure. created using the "Create New" procedure.
Notice the -c is NOT USED to add log ins to an existing .htpasswd file. The -c option creates a NEW file, containing only the first login.

This is what to type (or copy / paste /edit) to ADD a login to an existing .htpasswd file:

htpasswd .htpasswd UserName

Place the .htaccess file in the directory you wish to password protect with a path to the .htpasswd file.
.htpasswd can have other names, as long as the .htaccess file references it by the correct path and file name.
When .htaccess is placed in a folder/directory it password protects that dPassword Protection is done by adding a .htaccess file to the Folder you wish to add protection to.
There is another file .htaccess will reference typically named .htpasswd that can be named other names as desired.
Notice they both begin with a dot followed by ht (.ht). ice they both begin with a dot followed by ht (.ht).
Any file beginning with .ht will be hidden from view in any web browser viewing any folder containing it, by Apache Server.
The file will exist in the Folder, and be visible to you in Windows Explorer, or command prompt, but it will not be listed by Apache when anyone views the folder containing it, with any web browser. This is intentional!

There are many lines in the php.ini file that begin with a Semicolon.
Lines beginning with a Semicolon are ignored by PHP when it loads the php.ini file at start up.
This is much like the # in Apache Servers httpd.conf file.
The Semicolons are used to leave comments that are convenient to you, as well as disable, but store the code for optional features.

Adding PEAR to the default installation on this page is not very difficult.
When PHP was installed, it came with PEAR's installation, ready to install.
If you followed the default installation, look in your C:\php directory for the   go-pear.bat   file.
This go-pear.bat file is a batch file that does almost all of the installation of PEAR for you.
To install PEAR:

Double click the go-pear.bat file.
The setup will ask you some questions.
PEAR is to be installed in the    C:\php\PEAR    folder (Directory).
Next, after the batch file is done running, Double Click the newly generated PEAR_ENV.reg file that was created in the C:\php folder.
The PEAR Package Manager will be installed in the path, you specified during installation.
The php.ini file is already updated with the PATH to your PEAR Installation.
You may OPTIONALLY edit the php.ini file and remove the semicolon from in front of this line ;extension=php_dba.dll  if you want DBA for PEAR
You may OPTIONALLY edit the php.ini file and remove the semicolon from in front of this line ;extension=php_shmop.dll  if you want Shmop for PEAR. You may OPTIONALLY edit the php.ini file and remove the semicolon from in front of this line ;extension=php_ifx.dll  if you want informix extensions for PEAR. Just because you may optionally decide to load these modules with PHP for PEAR, does not necessarily mean you want them.
Restart (Stop / Start) Apache for changes to take effect.
PEAR is ready to go!

Installing Pearl in Windows:

Download the appropriate Pearl installation from the link above, based on you 32 bit or 64 bit Server.
Double click the file to Run the installation.
Accept all the defaults.

Configure httpd.conf for your CGI Directory path and ScriptAlias.
If you are using the httpd.conf file provided on this page, you are already mostly configured for Pearl.
The only thing you may wish to change, to get Pearl working, is the paths for ScriptAlias and the CGI Directory.

If you used the httpd.conf provided it already has you set up to use C:\cgi-bin   (Which you created at the beginning of this Guide)
When you are developing scripts, this path provides the same security as C:\Program Files\Apache Software Foundation\Apache2.2\cgi-bin, but it is much more convenient to access, than C:\Program Files\Apache Software Foundation\Apache2.2\cgi-bin

Perl adds C:\Perl\bin to the beginning of your Servers Path, which allows you to begin your scripts with "#!perl" or "#!c:/perl/bin/perl.exe".

Re-Boot your Computer to insure the new Windows Path will be loaded in the Windows Path.

Should you wish to add secure connections to your Server, in order to keep confidential data secure, or to perform financial transactions, you will want to enable ssl. The preconfigured httpd.conf file provided on this page already has most of the needed configuration done for you.
In order to activate ssl on your server, follow the instructions on the Installing SSL on Apache Server in Windows Page.

Installing MySQL Database Server in Windows:

Run the MSI file and use the following settings

Typical Setup:
Skip Sign-Up
Make sure "Configure the mySQL Server now" box is checked.
"Detailed Configuration"
"Developer Machine"
"Multifunctional Database"
"InnoDB Tablespace Settings" - leave everything default
"Decision Support (DSS)/OLAP"
Make sure "Enable TCP/IP Networking" is checked
Leave the port number at 3306 (at this point, if you have a firewall, it will usually try to access itself on the localhost)
"Standard Character Set"
Check "Install As Windows Service".
Leave "Include Bin Directory in Windows PATH" checked.
Enter your root password.
Click "execute"
Wait while MySQL completes its installation and set up.

Then open up your php.ini in a text editor and search for:
;extension=php_mysql.dll
Remove the ; in front of extension=php_mysql.dll
Search for:
;extension=php_mbstring.dll
Remove the ; in front of extension=php_mbstring.dll
Without the mbstring extension phpMyAdmin is unable to split strings correctly, which may result in unexpected results.
Restart Apache and check your error log for any errors.
If there are errors for php_mysql.dll either your extension directory isn't correct or windows can't find libmysql.dll

Installing phpMyAdmin in Windows:
Extract all the files in the archive into a "phpmyadmin: folder located in the Document Root of Apache (Where the website files Apache is hosting are located on your computer).
The folder "phpmyadmin" should be all lower case.
Make sure the files get extracted right into this directory, and not into
"phpmyadmin\phpMyAdmin-1.2.3". (the phpMyAdmin-1.2.3 will be a different version on your computer)

If this happens, using "My Computer", browse to (Apache Document Root)\phpmyadmin\phpMyAdmin-1.2.3".
From the browse window
Click the "Edit" drop down, and Click "Select All".
Right Click the selected files, and select "Cut".
Browse back one directory (Apache Document Root)\phpmyadmin" and Right Click, then select "Paste".
Right Click the phpMyAdmin-1.2.3 directory and click "Delete".
Click "Yes" when the confirm delete dialog comes up.

Start Notepad and open the file "(Apache Document Root)\phpmyadmin\config.inc.php".
If your machine does not have this file, then create it.
On some computers, this file might look like a real mess.
If this happens, close Notepad and open Wordpad (usually found in "Start">"All Programs">"Accessories">"WordPad") Open the "config.inc.php" file.
Everything should now look readable.
Click "File">"Save" to save this better looking version of the file.
Now re-open the "config.inc.php" with Notepad.
Find the line: cfg['Servers'][$i]['auth_type'] = 'config';
Change the line so that it reads: $cfg['Servers'][$i]['auth_type'] = 'cookie';
Find the line: $cfg['blowfish_secret'] = ''; Inside ''
put any word you want, like "best".
The line should look like: $cfg['blowfish_secret'] = 'best';
Click the "File" drop down and select "Save".
Close Notepad.

After Configuring phpMyAdmin, login with your web browser at http://yourIPaddress/phpmyadmin
Use "root" as the Username, and the root password you chose when installing MySQL as the password.

This adds a layer of protection to your server. This is done in the Servers httpd.conf file. This blocks Hackers from exploiting your Server, when you have no Firewall Rule blocking them already in place. You can't always know the IP Address of your next hacker! As soon as you see them in your Server log, you will want to add, or modify a Firewall Block Statement to deal with them, so they wont reach your server ever again! Most of the hackers are automated bots, running a scripted search for your resources, and vulnerabilities, and their bots User-Agent identifiers are almost always different than the conventional web browsers, used by the legitimate users of your Server. This makes screening the majority of those that reach your Server relatively simple!
As a bonus, when the hacker/bot gets the 403 Forbidden response, from blocking its User-Agent, they tend give up, and to cut short running their script, most of the time.

If you used this Installing Apache Server and PHP in Windows Guide, you will already have some examples of real User-Agents being blocked using "Deny from" rules in your Apache httpd.conf file. It should look something like this:

# Sets up User Agent List that can be Blocked.
# Example: SetEnvIf User-Agent "BadUA" UA
# Replace BadUA with the User-Agent identifier you wish to Block.
# The UA at the end of the statement is a Variable that will be tested in the Deny from statement later.
#  NoCase Makes SetEnvIf Case-insensitive.
# The "_" and "-" below are User-Agents common with hack attempts.
#
SetEnvIf User-Agent "^$" UA
SetEnvIf User-Agent "^_" UA
SetEnvIf User-Agent "^-" UA
SetEnvIfNoCase User-Agent "ZmEu" UA
SetEnvIfNoCase User-Agent "Python-urllib" UA
SetEnvIfNoCase User-Agent "Morfeus" UA
SetEnvIfNoCase User-Agent "MSIE 6.0" UA
SetEnvIfNoCase User-Agent "Windows 98" UA
SetEnvIfNoCase User-Agent "Firefox/3" UA
#
#
Order allow,deny
Allow from all

Deny from env=UA
# Deny from 31.210
# Deny from 50.22.232.171

In this example, the User-Agent to be blocked is in quotes.
It uses the Set Environment Variable based on User-Agent in the SetEnvIf User-Agent part of the statement.
The variable it sets is the "UA" at the end of the statement.
It then later tests to see if UA was set in the Deny from env=UA Statement.
The result is that if a User-Agent in your list is detected, access to your Server will be denied, and 403 Forbidden will be returned.
These rules could also be placed in your htaccess files. I prefer mine in the httpd.conf file.
The few Rules in this example block pretty much everything that has ever attacked my Server, and they where created specifically for my attackers.

Note: SetEnvIf User-Agent "Python-urllib" UA will also block "Python-urllib/2.4", or other versions of Python-urllib, as long as Python-urllib is found in the User-Agent identifier, any request Will Be Blocked, and return a 403 Forbidden response to your un-invited guest.
With SetEnvIf User-Agent "Mozilla/4.0" UA the User-Agent identifier must match "Mozilla/4.0" specifically, if I do not wish to block other versions of Mozilla Firefox by only using "Mozilla". Version 4.0 is the only version that would match the rule, and be blocked.
Windows 98 using Internet Explorer 6.0 has been commonly used as an identifier in attempted hacks on my Server, and they are outdated, so, I block them.
Look in your access.log files for the User-Agent identifiers you are being hacked / attacked with.
Make sure that if the User-Agent identifier does not correspond to any potentially valid Web Browser used for valid access to Your Web Server, that you block that User-Agent from having any access!
When you see them in your access.log, also make sure to block their IP Address (or potential range of IP Addresses) in your Firewall, as well.
Blocking access to hackers with your Firewall is the best method, but if you can catch the ones that are not yet Blocked by the Firewall, by their bogus User-Agent, they will not have access to anything before you can block them with your Firewall. This adds another layer of Security.

Also Note:
^ proceeding a character will indicate that the character is literally located at the beginning of the line/string being tested.
$ after a character will indicate that the character is literally at the end of a line/string being tested.
The test string ^$ indicates a null string. The ^$ is used to test to see if User-Agent information is blank.

Here is a list of Potentially BAD User-Agents.

If you run Apache Server on a Windows platform, you have probably noticed hacker attempts in your log file.
You have probably also noticed that in order to block hacker attempts you must add "Deny from" statements to your httpd.conf file, because Windows Firewall has NO realistic provision to do such a thing.
While adding "Deny from" statements may deny them access to the server, the server still must handle the requests, and sends back the 403 Forbidden notifications.
Many hacking attempts are scripted. They sometimes ignore errors, and keep on trying, as they seek accessible resources to exploit.
While they will never find any, it still uses your internet bandwidth, server bandwidth, and fills up your logs.
"Deny from" rules are still good to have in your Server's httpd.conf file for the list of User-Agents from the scripted hack attempts to your Server, as there is no way to know what IP Address your next hacker will be coming from. Blocking the User-Agent of the programs they use to hack your Server will keep them out, until you can block their range of possible IP Addresses.
A better solution than blocking IP Addresses in "Deny from" statements is to be able to block them with your Firewall, before their requests ever get to your Server!
You need a way to block inbound requests by IP Address.
Attempts may come from Dynamic IP Addresses. These change every time the hacker logs in to their service provider.
Service providers have blocks of sequential IP Addresses which they can assign to their users.
This means your hacker could have a new IP Address, by just logging back in.
You need to be able to determine what range of sequential IP Addresses their service provider has available to assign them, and block them ALL.
You also need to be able to define the entire sequential range of addresses for your Firewall to block, without having to enter them one at a time.
You will need to be able to do Packet Filtering in your Firewall by IP Address, and ranges of IP address.

THERE IS A SOLUTION!!!

Click Here!!!

You will notice that your access and error logs grow over time, and eventually get rather large.
Having to append to the end of a large file, every time there is an event, slows down your Server.
For this reason many people remove the log file and start over with an empty log file, at an appropriate time.
This procedure is known as log rotation.
There are many methods of doing this, and any that works for you is acceptable.
The problem you may have on your Windows based Apache Server is that the built in log rotation feature is still buggy in Windows.
I have solved this for myself, by creating a log rotation batch file.
The batch file I created rotates my Apache Server, Filezilla FTP Server, and my Server Chat Logs all from one batch file.
You may only have the Apache Server logs to rotate. I have more.
I will share with you my batch file code as an example, and you may modify it to suit your personnel needs.

Copy and Paste the code below, into a text file, with a .bat extension:

@echo off :: Name - log_rotate.bat :: Description - Apache Server Log File Rotation Manager :: :: ======================================================== :: setup variables and parameters :: ======================================================== :: generate date and time variables for /f "tokens=2,3,4 delims=/ " %%i in ('date /T') do set date=%%k-%%i-%%j for /f "tokens=1,2 delims=: " %%i in ('time /T') do set time=%%i%%j set tdstamp=%date%_%time% echo wsh.echo date-1 > %temp%\tmp.vbs for /f "tokens=1-3 delims=/" %%a in ( 'cscript.exe //nologo %temp%\tmp.vbs' ) do (set mm=0%%a& set dd=0%%b& set yr=%%c) del %temp%\tmp.vbs set M=%mm% set D=%dd% set Y=%yr% set fzdate=%Y%-%M%-%D% :: ======================================================== :: turn over log files :: ======================================================== :: change to the apache log file directory :: cd /C "C:\Program Files\Apache Software Foundation\Apache2.2\logs\" :: NOTE E:\Backup\Apache Server\Apache Windows\Logs is my storage location Path :: Copy and Date/time stamp Server Logs to Backup Location :: stop Apache Service, Move log files and restart Apache Service net stop "apache2.2" move "C:\Program Files\Apache Software Foundation\Apache2.2\logs\access.log" "E:\Backup\Apache Server\Apache Windows\Logs\%tdstamp%_access.log" move "C:\Program Files\Apache Software Foundation\Apache2.2\logs\error.log" "E:\Backup\Apache Server\Apache Windows\Logs\%tdstamp%_error.log" move "C:\Program Files\Apache Software Foundation\Apache2.2\logs\ssl_request.log" "E:\Backup\Apache Server\Apache Windows\Logs\%tdstamp%_ssl_request.log" net start "apache2.2" :: Backup Chat Log move "E:\www\magicchat\data\private\logs\cd0eaeaf61a30d4712f78b0cb01594e5\chat.log" "E:\Backup\Apache Server\Apache Windows\Logs\Chat\%tdstamp%_chat.log" copy "E:\Backup\Apache Server\Apache Windows\Logs\Chat\chat.log" "E:\www\magicchat\data\private\logs\cd0eaeaf61a30d4712f78b0cb01594e5\chat.log" :: Move Yesterdays FileZilla Log move "C:\Program Files\FileZilla Server\Logs\fzs-%fzdate%.log" "E:\Backup\Apache Server\Apache Windows\Logs\FTP\fzs-%fzdate%.log"

After you have a functioning batch file for your use, you can use Windows Task Scheduler to schedule your batch file to run on a regular schedule.
I run mine once a day.
You will have to edit, at the very least, the path statements in this batch file to correspond to the correct paths on your computer.
You will probably also need to comment out, or remove the code related to my Chat and FTP Server as well. This is merely an example.

With daily Log Rotation, your server will accumulate many log files, and it will become desirable to archive the accumulated logs into a more manageable date stamped archive file.
The archive file will contain the many log files compressed into one date stamped archive file, which will take up much less hard drive space.
I archive my logs on a monthly schedule.
This results in a monthly date stamped zip file, containing a month worth of daily logs.
The original daily log files can then be deleted.
This is another task which can easily be automated, and scheduled.
To do so you will need a Command Line Zip Utility.
For my server I use the FREE IZArc Command Line Utility.
If you do not have a command line zip utility, get IZArc command line utility HERE.
Run the IZArcCL.exe file, and complete the installation.
The IZArc folder needs to be in the path for the command line utility to work.
In order to put IZArc in the Windows Path Statement, so that it will function when used, do the following:
Highlight the following text for your operating system, below in bold, Right Click on it, and Click Copy:

32 bit Windows:
;C:\Program Files\IZArc

64 bit Windows Path:
;C:\Program Files (x86)\IZArc

Click Start >> Control Panel >> System >> Advanced Settings >> Environment Variables

Under "System Variables" Scroll down to the Variable named "Path".

Click on "Path" to Highlight it, and Click "Edit".

Click in the box named "Variable Value" (you should see your cursor there, and the blue highlight should go away).

Press the "End" Key on your Keyboard.

Hold down the "Ctrl" (Control) Key on the Keyboard, and while still holding the "Ctrl" Key down, Press the "V" key once.

You should see ;C:\Program Files\IZArc or ;C:\Program Files (x86)\IZArc added to the end of the line of text in the box named "Variable Value".

Click "OK".

Re-Boot your Computer to insure the new Path will be loaded in the Windows Path.

Below is an example of a batch file I wrote to handle the monthly Log File Archiving task:

The batch file I created Archives my Apache Server, Filezilla FTP Server, and my Server Chat Logs all from one batch file.
You may only have the Apache Server logs to Archive. I have more.
I will share with you my batch file code as an example, and you may modify it to suit your personnel needs.

Copy and Paste the code below, into a text file, with a .bat extension:

@echo off :: Name - scheduled_log_archive.bat :: Description - Apache Server Log File Archive Manager :: :: History :: Date Authory Change :: 10-Dec-2011 bestyoucanget Original :: ======================================================== :: setup variables and parameters :: ======================================================== :: generate date and time variables for /f "tokens=2,3,4 delims=/ " %%i in ('date /T') do set date=%%k-%%i-%%j set tstamp=%date% echo wsh.echo date-1 > %temp%\tmp.vbs for /f "tokens=1-3 delims=/" %%a in ( 'cscript.exe //nologo %temp%\tmp.vbs' ) do (set mm=%%a& set dd=%%b& set yr=%%c) del %temp%\tmp.vbs set M=%mm% set D=%dd% set Y=%yr% IF %M% LSS 10 Set M=0%M% IF %D% LSS 10 Set D=0%D% set fzdate=%Y%-%M%-%D% :: ======================================================== :: Archive Server Logs Monthly to Backup Location :: ======================================================== :: NOTE E:\Backup\Apache Server\Apache Windows\Logs is my storage location Path :: IZARCC Command Line Utility available for FREE at izarc.org :: IZACC must be in the Windows Path Statement :: IZARCC archivename.zip C:\path\filename.ext :: Does not allow Spaces in the file name, so use a "Folder~1" formatted folder names in the path :: Change to the IZARCC file directory if not putting IZARCC in the Windows Path Statement :: cd /C "C:\Program Files\IZArc" :: cd /C "C:\Program Files (x86)\IZArc" :: Run 1 min after Backup on the First or 12:02 AM on the first of the Month :: Example- My actual Path with spaces in the folder names in the path commented out below- followed by what works :: IZARCC E:\Backup\Apache Server\Apache Windows\Logs\templog.zip E:\Backup\Apache Server\Apache Windows\Logs\*.log IZARCC E:\Backup\Apache~1\Apache~1\Logs\%tstamp%_log.zip E:\Backup\Apache~1\Apache~1\Logs\*.log Del E:\Backup\Apache~1\Apache~1\Logs\*.log :: Archive Chat Logs IZARCC E:\Backup\Apache~1\Apache~1\Logs\Chat\%tstamp%_chat_log.zip E:\Backup\Apache~1\Apache~1\Logs\Chat\*_chat.log Del E:\Backup\Apache~1\Apache~1\Logs\Chat\*.log :: Archive FileZilla Logs IZARCC E:\Backup\Apache~1\Apache~1\Logs\FTP\%fzdate%_ftp_log.zip E:\Backup\Apache~1\Apache~1\Logs\FTP\fzs-*.log Del E:\Backup\Apache~1\Apache~1\Logs\FTP\fzs-*.log

After you have a functioning batch file for your use, you can use Windows Task Scheduler to schedule your batch file to run on a regular schedule.
I run mine once a month.
You will have to edit, at the very least, the path statements in this batch file to correspond to the correct paths on your computer.
Remember IZARCC does not allow Spaces in folder names in the path, so change the names to a truncated name with a ~1 at the end.
You will probably also need to comment out, or remove the code related to my Chat and FTP Server as well. This is merely an example.

Guide to Setting Up Virtual Hosting on Apache Server in Windows

You may wish to host multiple domains, IP addresses, or Ports on your Apache Server.
Virtual Hosts allows you to host multiple sites with one Server.
You can configure as many as you need, provided your server hardware can handle the load.
There is a Guide to setting up Virtual Hosting, complete with copy and paste httpd-vhosts.conf file, and it is compatible with th httpd.conf file on this page. Simply follow the guide to set up the httpd-vhosts.conf provided, your Firewall and Router, and remove a hash # in your httpd.conf file.
Reboot Apache, and start setting up the site on your new virtual host.

There is a Free Performance Benchmarking tool included with Apache Serer, which is useful for tweaking some settings in your httpd.conf file.
The tool is called ab. There is documentation for ab on Apache's web site, HERE.

Here is a sample command line instruction:
ab -n100 -c10 -k -e C:\abtest-k-128-10.csv http://192.168.0.10:80/index.htm

ab is the name of the executable file (ab.exe)

ab is located here:

C:\Program Files\Apache Software Foundation\Apache2.2\bin

The -n100 sets the total number of requests performed for the benchmarking session to 100.
In other words it will make 100 requests to the server, total, during the test.

The -c10 sets the number of multiple requests to send to the server at one time, to 10.
Note that this is a lower case "c". Do Not capitalize the "C", or you will be setting an entirely different parameter!

The -k tells ab to use the servers KeepAlive feature, during the tests.
Removing the -k will do the tests without the KeepAlive feature.
When tuning KeepAlive settings, you will definitely want the -k in your command string.

The -e causes ab to write a CSV file which contains for each percentage of the requests, the time (in milliseconds) it took to serve them.

The http://192.168.0.10:80/index.htm  contains 3 parameters. The address to be tested, followed by a colon , followed by the Port number to test on, and finally a / followed by the name of the file to request, and download, for the test to benchmark.
This command line instruction remains on the Local Area Network, as you can see by the address in the command line.
This eliminates traversing the routers firewall, and concentrates the test on only the Server.
The Internet IP Address can be substituted when you adjust settings in your router, for performance, although there are not many of those.
It could be helpful for troubleshooting router settings, though.

NOTE: ab will test Apache with a User Agent Identifier that is blocked by the current configuration in the httpd.conf file.
In order for ab to be able to perform these tests, you must add a hash # mark in front of the line:
Deny from env=UA
so it looks like this:  
#Deny from env=UA
Save httpd.conf with this change, and restart Apache, for the new setting to be effective.
Run your tests with ab, and then remove the # hash from the    Deny from env=UA   line, save httpd.conf, and restart Apache, again.
While the # hash is in place, in front of  Deny from env=UA, Apache will not block any bogus user agents.
The lack of the   Deny from env=UA   in httpd.conf, as a result of the # hash, leaves your server available to many hackers hacking attempts.
Only run Apache with the # hash in the httpd.conf in front of   Deny from env=UA   while testing with ab.

You can come up with many tests to have ab perform on your server, depending on your needs!

Apache Log Viewer is a great FREE Log Viewer to keep an eye on things with.
It can look at the real time live access and error log files, as well as backed up ones.
It has many features, that far surpass viewing the log files in notepad. Well worth having!!!
Keep in mind, that this is a log file viewer, not a log report generator.

Welant Log Analyzer Trends is a FREE Log Report generator.
It limits the results for its FREE version to a depth of the top 20, but may be adequate for personnel use.
It will analyze your Servers log files, allow you to add more log files later (so you can update your reports), and generate all the files which allow you to view your report in a web browser. The reports file is named index.html, and it will place it in a \trend\loganalysis folder.

Notepad++ is a handy tool for editing the many configuration text based files you will be managing, it lets you open tabbed text files, which is handy.

Filezilla FTP Server is a great way to add FTP access to your Server.
An FTP Server requires Forwarding of Port 21on your Router (the default FTP Port).

PHPFreeChat is a Chat Service you can add to your Server for FREE. Download it HERE.
It runs completely on your Server, and can be run with or without MySQL (NO SQL Required).
It can also be customized.

This is Optional, and not required in order to use Apache Server, or PHP. This also requires the installation of a Mail Transport Agent!
For most people the sendmail feature that was already part of the install above is what you need so that your server can send email from PHP.
For those who actually need a resident Mail Transport Agent, and own a Domain to associate with it, to get it functioning:
These are the lines in the php.ini file that you may wish to adjust regarding sending email with PHP on your Server.

[mail function]
; For Win32 only.
;SMTP = localhost
;mail.mydomain.com
;smtp_port = 25

; For Win32 only.
;sendmail_from = webmaster@mydomain.com

; For Unix only. You may supply arguments as well (default: "sendmail -t -i").
sendmail_path = C:\sendmail\sendmail.exe

; Force the addition of the specified parameters to be passed as extra parameters
; to the sendmail binary. These parameters will always replace the value of
; the 5th parameter to mail(), even in safe mode.
;mail.force_extra_parameters =

As you can see you can specify your SMTP Servers Domain or IP Address, as well as its Port Number, but there is no means of Authentication provided. That means, that there is no ability to log in to an email account with a User ID and Password.
The default installation already addresses this, with the addition of the sendmail function to Windows, much the same way you would add any other Mail Transport Agent to PHP in Apache. The lines of the php.ini file above, are the actual ones in use by the default installation provided on this web page. Notice the "For Win32 only." section IS NOT used, and the "sendmail_path =" in the "For Unix only." section IS being used, even though you are running Apache and PHP in Windows. The "sendmail_path =" line sets the path to the Mail Transport Agent that PHP will use.
The Mail Transport Agent handles the issue of Authentication (Usernames and Passwords - login).
If you have your own Domain, and MX Records, pointed at your IP Address, and wish to use your own Mail Server (Mail Transport Agent), you will want to point the path of the "sendmail_path =" line to your Mail Server (Mail Transport Agent) software.
If you do not have a Domain Name and MX Records pointing at your IP Address, then you will want to use the sendmail feature already added to the default installation provided on this web page. It will allow you to use the email service from your ISP or other email services, to send email.