You may also need to have a
<directory></directory> section to allow you access to the
F:/test_/ directory:
- Code: Select all
#
# 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.
<IfModule alias_module>
Alias /tphp "F:/test_/"
</IfModule>
<Directory "F:/test_/">
AllowOverride None
Options None
Order allow,deny
Allow from all
</Directory>
Experiment with the above and read the commented lines
# in the
xampp/apache/conf/httpd.conf as they always give you some very useful clues if you get error messages.
A 403 error is an access permission error and the above commented lines explain that you need to set a
<directory></directory> permission section to allow or deny access.
Access is denied by default in the
httpd.conf file so you have to change that behavior if you don't want a 403 error.
- Code: Select all
#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
#
# First, we configure the "default" to be a very restrictive set of
# features.
#
<Directory />
Options FollowSymLinks
AllowOverride None
Order deny,allow
Deny from all
</Directory>
But don't change this default setting though. Just set a
<directory></directory> section for the directory you want to change permissions for. As in my first example above.
So, why XAMPP's server neglects the php.ini inside its root folder?
Xampp's Apache is using the Windows Registry first.
If it finds another php.ini file location in the registry then it assumes you have another php installation somewhere you want to use (which you had). This is perfectly normal proceedure.
You changed the php.ini file extension on the one you don't want to use so XAMPP Apache could not locate the one in the Windows Registry and so it used it's own default php.ini file, which is all it knows how to do and again this is perfectly normal.
HTH and good luck