WampServer

Hello,

I'm trying to get my "C:\wamp\www\users\website_1" and "C:\wamp\www\users\website_2" on to the World Wide Web. I have two domains i.e server.homeftp.net and apache.homeftp.net. No one will be able to access these at the moment as access is denied.

Although when access is allowed both domains go to the localhost page (WAMP 5 page), where my friends have to click on the folder and test my websites.

This is so annoying and not very professional, if somebody could help it would be so greatful. I have looked at the "[jlbn.net]; website and i couldn't find anything. I also looked at the "CyberSpatium" manual and i couldn't find anything.

I have already done the "12. Setup Virtual Host for local network", which i looked at the "[jlbn.net]; website. This is not working neither. All ports are allowed on my firewall and router.

Please help,

Thanks,
Mitesh



Post Edited (10-28-07 01:39)

Quote

Although when access is allowed both domains go to the localhost page (WAMP 5 page), where my friends have to click on the folder and test my websites.

This is so annoying and not very professional, if somebody could help it would be so greatful. I have looked at the "[jlbn.net]; website and i couldn't find anything.

Because it's still in progress as seen on my website as follows:

Quote

11. Setup Virtual Host for worldwide access as well as run multiple site(s)/domain(s) on 1 ip:
Coming soon

Quote

I have already done the "12. Setup Virtual Host for local network", which i looked at the "[jlbn.net]; website. This is not working neither. All ports are allowed on my firewall and router.

Hope you follow the instruction precisely

When you have proper setup, each site should go to its assigned location; for example:

[www.jlbn.net] (all access go to c:/wamp/www/jlbn)
[test.jlbn.net] (all access go to c:/wamp/www/test)
[downloads.jlbn.net] (all access go to c:/wamp/www/downloads)
[guide.jlbn.net] (all access go to c:/wamp/www/guide)

Have fun,

[test.jlbn.net] (Sample Testing Codes for PHP, MySQL, ASP.net, SQL, JSP)
[www.jlbn.net] (Basic Guide for WAMP & Add-ons)

Post Edited (10-28-07 11:28)

Post Edited (10-28-07 11:28)

Hello,

I have followed the steps, and in the file: "C:\wamp\Apache2\conf\extra\httpd-vhosts.conf" , this is where i started to change the scripts to:

--------------------------------------------------------------------------------------------------------------------------------------------

#
# Virtual Hosts
#
# If you want to maintain multiple domains/hostnames on your
# machine you can setup VirtualHost containers for them. Most configurations
# use only name-based virtual hosts so the server doesn't need to worry about
# IP addresses. This is indicated by the asterisks in the directives below.
#
# Please see the documentation at
# <URL:[httpd.apache.org];
# for further details before you try to setup virtual hosts.
#
# You may use the command line option '-S' to verify your virtual host
# configuration.

#
# Use name-based virtual hosting.
# NameVirtualHost *:80

NameVirtualHost 90.202.233.6:80
NameVirtualHost 90.202.233.6:81
NameVirtualHost 90.202.233.6:8080

<VirtualHost 90.202.233.6:80>
ServerName localhost
DocumentRoot c:\wamp\www\users\website1\public_html
ErrorLog c:\wamp\www\users\website1\logs\error.log
CustomLog c:\wamp\www\users\website1\logs\access.log common
<Directory c:\wamp\www\users\website1\public_html>
Options Indexes FollowSymLinks Includes
Order deny,allow
Deny from all
Allow from 127.0.0.1
</Directory>
</VirtualHost>

<VirtualHost 90.202.233.6:81>
ServerName localhost
DocumentRoot c:\wamp\www\users\website2\public_html
ErrorLog c:\wamp\www\users\website2\logs\error.log
CustomLog c:\wamp\www\users\website2\logs\access.log common
<Directory c:\wamp\www\users\website2\public_html>
Options Indexes FollowSymLinks Includes
Order deny,allow
Deny from all
Allow from 127.0.0.1
</Directory>
</VirtualHost>

<VirtualHost 90.202.233.6:8080>
ServerName localhost
DocumentRoot c:\wamp\www\users\website3\public_html
ErrorLog c:\wamp\www\users\website3\logs\error.log
CustomLog c:\wamp\www\users\website3\logs\access.log common
<Directory c:\wamp\www\users\website3\public_html>
Options Indexes FollowSymLinks Includes
Order deny,allow
Deny from all
Allow from 127.0.0.1
</Directory>
</VirtualHost>


#
# VirtualHost example:
# Almost any Apache directive may go into a VirtualHost container.
# The first VirtualHost section is used for all requests that do not
# match a ServerName or ServerAlias in any <VirtualHost> block.
#
<VirtualHost *:80>
ServerAdmin webmaster@dummy-host.localhost
DocumentRoot /www/docs/dummy-host.localhost
ServerName dummy-host.localhost
ServerAlias www.dummy-host.localhost
ErrorLog logs/dummy-host.localhost-error_log
CustomLog logs/dummy-host.localhost-access_log common
</VirtualHost>

<VirtualHost *:80>
ServerAdmin webmaster@dummy-host2.localhost
DocumentRoot /www/docs/dummy-host2.localhost
ServerName dummy-host2.localhost
ErrorLog logs/dummy-host2.localhost-error_log
CustomLog logs/dummy-host2.localhost-access_log common
</VirtualHost>

--------------------------------------------------------------------------------------------------------------------------------------------

As i saved it in that path i was getting an memory error and Apache wouldn't work. So then i set it back to normal as how it was before and Apache would work.

So i then tried it in the path "C:\wamp\Apache2\conf\default\httpd-vhosts.conf" and for some reason Apache works but when i type in "[]; i get an error:
--------------------------------------------------------------------------------------------------------------------------------------------

403 Forbidden

You don't have permission to access / on this server.

--------------------------------------------------------------------------------------------------------------------------------------------
As when i type "[]; and "[];, i get the normal WAMP5 Homepage (localhost page), where i have to chose the projects from

I know i must be doing something wrong here.

please help,
Thanks,
Mitesh



Post Edited (10-28-07 11:31)

First, take out those two examples

Second, through wamp tray icon, put your server in online mode

Third, make sure to enable all those ports 80, 81, 8080 in all firewalls and routers

Fourth, he he... he he... ;-) that part was written a pretty while ago for a much older wamp version, and I might have to check to make sure it still works w/ this wamp version

Have fun,

[test.jlbn.net] (Sample Testing Codes for PHP, MySQL, ASP.net, SQL, JSP)
[www.jlbn.net] (Basic Guide for WAMP & Add-ons)

Hello Expert,

How do i set the domain names to my project index page, like your website. As when i type the domain now "server.homeftp.net" it keeps going to WAMP homepage. I want it to go to the project folder index page i.e. "C:\wamp\www\users\Website_1\public_html\index.php".

Thanks alot for the help,
Mitesh

Hi,

If you use a domain name, instead of an IP address, to access the site, your virtual host needs to be set up to listen to the name, not the IP address. Here are the key changes you should do:

#
# Use name-based virtual hosting.
#
NameVirtualHost *:80

If you use domain names, you should not list the IP address and port as the name of the virtual host. Therefore, remove the lines:

NameVirtualHost 90.202.233.6:80
NameVirtualHost 90.202.233.6:81
NameVirtualHost 90.202.233.6:8080

Further, instead of:

<VirtualHost 90.202.233.6:80>

you should have:

<VirtualHost *:80>
ServerName example.com
... and so on

When the server name is specified in the <VirtualHost *:80> tag, the virtual host responds to HTTP requests addressed to that domain.

Last, you specified:

Order deny,allow
Deny from all
Allow from 127.0.0.1

You should have:

Order allow,deny
Allow from all

so that the requests coming from the internet, not just from the browser running in the WAMP server itself, are allowed.

You can limit the access to your server during testing by specifying external IP addresses in the Allow statement, until you get the necessary security fully sorted out.

Regards,



toivo
Sydney, Australia

Hi,

I have done this to the "httpd.conf" script

#
# Virtual Hosts
#
# If you want to maintain multiple domains/hostnames on your
# machine you can setup VirtualHost containers for them. Most configurations
# use only name-based virtual hosts so the server doesn't need to worry about
# IP addresses. This is indicated by the asterisks in the directives below.
#
# Please see the documentation at
# <URL:[httpd.apache.org];
# for further details before you try to setup virtual hosts.
#
# You may use the command line option '-S' to verify your virtual host
# configuration.

#
# Use name-based virtual hosting.
#
NameVirtualHost *:80

<VirtualHost *:80>
ServerName apache.getmyip.com
DocumentRoot c:\wamp\www\users\website1\public_html
ErrorLog c:\wamp\www\users\website1\logs\error.log
CustomLog c:\wamp\www\users\website1\logs\access.log common
<Directory c:\wamp\www\users\website1\public_html>
Options Indexes FollowSymLinks Includes
Order deny,allow
Deny from all
Allow from all
</Directory>
</VirtualHost>

#
# VirtualHost example:
# Almost any Apache directive may go into a VirtualHost container.
# The first VirtualHost section is used for all requests that do not
# match a ServerName or ServerAlias in any <VirtualHost> block.
#
<VirtualHost *:80>
ServerAdmin webmaster@dummy-host.localhost
DocumentRoot /www/docs/dummy-host.localhost
ServerName dummy-host.localhost
ServerAlias www.dummy-host.localhost
ErrorLog logs/dummy-host.localhost-error_log
CustomLog logs/dummy-host.localhost-access_log common
</VirtualHost>

<VirtualHost *:80>
ServerAdmin webmaster@dummy-host2.localhost
DocumentRoot /www/docs/dummy-host2.localhost
ServerName dummy-host2.localhost
ErrorLog logs/dummy-host2.localhost-error_log
CustomLog logs/dummy-host2.localhost-access_log common
</VirtualHost>


-------------------------------------------------------------------------------------------------------------------

And to the "httpd.conf" script i have uncommented the line below:

# Virtual hosts
Include conf/extra/httpd-vhosts.conf

-------------------------------------------------------------------------------------------------------------------

As the whole script of "httpd.conf" is listed below:

#
# This is the main Apache HTTP server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:[httpd.apache.org]; for detailed information.
# In particular, see
# <URL:[httpd.apache.org];
# for a discussion of each configuration directive.
#
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
# with ServerRoot set to "C:/Program Files/Apache Software Foundation/Apache2.2" will be interpreted by the
# server as "C:/Program Files/Apache Software Foundation/Apache2.2/logs/foo.log".
#
# NOTE: Where filenames are specified, you must use forward slashes
# instead of backslashes (e.g., "c:/apache" instead of "c:\apache".
# If a drive letter is omitted, the drive on which Apache.exe is located
# will be used by default. It is recommended that you always supply
# an explicit drive letter in absolute paths, however, to avoid
# confusion.
#

# ThreadsPerChild: constant number of worker threads in the server process
# MaxRequestsPerChild: maximum number of requests a server process serves
ThreadsPerChild 250
MaxRequestsPerChild 0

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# Do not add a slash at the end of the directory path. If you point
# ServerRoot at a non-local disk, be sure to point the LockFile directive
# at a local disk. If you wish to share the same ServerRoot for multiple
# httpd daemons, you will need to change at least LockFile and PidFile.
#
ServerRoot "c:/wamp/apache2"

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
#
#Listen 12.34.56.78:80
Listen 80
#Listen 81
#Listen 8080
#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
#
# Example:
# LoadModule foo_module modules/mod_foo.so
#
LoadModule actions_module modules/mod_actions.so
LoadModule alias_module modules/mod_alias.so
LoadModule asis_module modules/mod_asis.so
LoadModule auth_basic_module modules/mod_auth_basic.so
#LoadModule auth_digest_module modules/mod_auth_digest.so
#LoadModule authn_anon_module modules/mod_authn_anon.so
#LoadModule authn_dbm_module modules/mod_authn_dbm.so
LoadModule authn_default_module modules/mod_authn_default.so
LoadModule authn_file_module modules/mod_authn_file.so
#LoadModule authz_dbm_module modules/mod_authz_dbm.so
LoadModule authz_default_module modules/mod_authz_default.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_user_module modules/mod_authz_user.so
LoadModule autoindex_module modules/mod_autoindex.so
LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule cgi_module modules/mod_cgi.so
#LoadModule dav_module modules/mod_dav.so
#LoadModule dav_fs_module modules/mod_dav_fs.so
#LoadModule deflate_module modules/mod_deflate.so
LoadModule dir_module modules/mod_dir.so
LoadModule env_module modules/mod_env.so
#LoadModule expires_module modules/mod_expires.so
#LoadModule file_cache_module modules/mod_file_cache.so
#LoadModule headers_module modules/mod_headers.so
LoadModule imagemap_module modules/mod_imagemap.so
LoadModule include_module modules/mod_include.so
#LoadModule info_module modules/mod_info.so
LoadModule isapi_module modules/mod_isapi.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule mime_module modules/mod_mime.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
#LoadModule proxy_module modules/mod_proxy.so
#LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
#LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
#LoadModule proxy_connect_module modules/mod_proxy_connect.so
#LoadModule proxy_http_module modules/mod_proxy_http.so
#LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule negotiation_module modules/mod_negotiation.so
#LoadModule rewrite_module modules/mod_rewrite.so
LoadModule setenvif_module modules/mod_setenvif.so
#LoadModule speling_module modules/mod_speling.so
#LoadModule status_module modules/mod_status.so
#LoadModule unique_id_module modules/mod_unique_id.so
LoadModule userdir_module modules/mod_userdir.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
#LoadModule ssl_module modules/mod_ssl.so
LoadModule php5_module "c:/wamp/php/php5apache2_2.dll"

# '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 webmaster@localhost

#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
#
ServerName localhost:80

#
# 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:/wamp/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 deny,allow
Deny from all
allow from 192.168.0.2
allow from 86.8.209.99
Satisfy all
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "C:/wamp/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
# [httpd.apache.org]
# for more information.
#
Options Indexes FollowSymLinks

#
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be "All", "None", or any combination of the keywords:
# Options FileInfo AuthConfig Limit
#
AllowOverride all

#
# Controls who can get stuff from this server.
#
# onlineoffline tag - don't remove
Order Deny,Allow
Deny from all
Allow from 127.0.0.1
allow from 192.168.0.2
allow from 86.8.209.99

</Directory>

#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
<IfModule dir_module>
DirectoryIndex index.php index.php3 index.html index.htm index.html.var
</IfModule>

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch "^\.ht">
Order allow,deny
Deny from all
</FilesMatch>

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog ../logs/apache_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
</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 [localhost]

#
# 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:/wamp/Apache2/cgi-bin/"

</IfModule>

#
# "C:/Program Files/Apache Software Foundation/Apache2.2/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "c:/wamp/apache2/cgi-bin">
AllowOverride None
Options None
Order allow,deny
Allow from all
</Directory>

#
# Apache parses all CGI scripts for the shebang line by default.
# This comment line, the first line of the script, consists of the symbols
# pound (#) and exclamation (!) followed by the path of the program that
# can execute this specific script. For a perl script, with perl.exe in
# the C:\Program Files\Perl directory, the shebang line should be:

#!c:/program files/perl/perl

# Note you _must_not_ indent the actual shebang line, and it must be the
# first line of the file. Of course, CGI processing must be enabled by
# the appropriate ScriptAlias or Options ExecCGI directives for the files
# or directory in question.
#
# However, Apache on Windows allows either the Unix behavior above, or can
# use the Registry to match files by extention. The command to execute
# a file of this type is retrieved from the registry by the same method as
# the Windows Explorer would use to handle double-clicking on a file.
# These script actions can be configured from the Windows Explorer View menu,
# 'Folder Options', and reviewing the 'File Types' tab. Clicking the Edit
# button allows you to modify the Actions, of which Apache 1.3 attempts to
# perform the 'Open' Action, and failing that it will try the shebang line.
# This behavior is subject to change in Apache release 2.0.
#
# Each mechanism has it's own specific security weaknesses, from the means
# to run a program you didn't intend the website owner to invoke, and the
# best method is a matter of great debate.
#
# To enable the this Windows specific behavior (and therefore -disable- the
# equivilant Unix behavior), uncomment the following directive:
#
#ScriptInterpreterSource registry
#
# The directive above can be placed in individual <Directory> blocks or the
# .htaccess file, with either the 'registry' (Windows behavior) or 'script'
# (Unix behavior) option, and will override this server default option.
#

#
# DefaultType: the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value. If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain

<IfModule mime_module>
#
# TypesConfig points to the file containing the list of mappings from
# filename extension to MIME-type.
#
TypesConfig conf/mime.types

#
# AddType allows you to add to or override the MIME configuration
# file specified in TypesConfig for specific file types.
#
#AddType application/x-gzip .tgz
#
# AddEncoding allows you to have certain browsers uncompress
# information on the fly. Note: Not all browsers support this.
#
#AddEncoding x-compress .Z
#AddEncoding x-gzip .gz .tgz
#
# If the AddEncoding directives above are commented-out, then you
# probably should define those extensions to indicate media types:
#
AddType application/x-compress .Z
AddType application/x-gzip .gz .tgz
AddType application/x-httpd-php .php
AddType application/x-httpd-php .php3
#
# AddHandler allows you to map certain file extensions to "handlers":
# actions unrelated to filetype. These can be either built into the server
# or added with the Action directive (see below)
#
# To use CGI scripts outside of ScriptAliased directories:
# (You will also need to add "ExecCGI" to the "Options" directive.)
#
#AddHandler cgi-script .cgi

# For type maps (negotiated resources):
#AddHandler type-map var

#
# Filters allow you to process content before it is sent to the client.
#
# To parse .shtml files for server-side includes (SSI):
# (You will also need to add "Includes" to the "Options" directive.)
#
#AddType text/html .shtml
#AddOutputFilter INCLUDES .shtml
</IfModule>

#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type. The MIMEMagicFile
# directive tells the module where the hint definitions are located.
#
#MIMEMagicFile conf/magic

#
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
#
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 [localhost]
#

#
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall is used to deliver
# files. This usually improves server performance, but must
# be turned off when serving from networked-mounted
# filesystems or if support for these functions is otherwise
# broken on your system.
#
#EnableMMAP off
#EnableSendfile off

# Supplemental configuration
#
# The configuration files in the conf/extra/ directory can be
# included to add extra features or to modify the default configuration of
# the server, or you may simply copy their contents here and change as
# necessary.

# Server-pool management (MPM specific)
#Include conf/extra/httpd-mpm.conf

# Multi-language error messages
#Include conf/extra/httpd-multilang-errordoc.conf

# Fancy directory listings
#Include conf/extra/httpd-autoindex.conf

# Language settings
#Include conf/extra/httpd-languages.conf

# User home directories
#Include conf/extra/httpd-userdir.conf

# Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf

# Virtual hosts
Include conf/extra/httpd-vhosts.conf

# Local access to the Apache HTTP Server Manual
#Include conf/extra/httpd-manual.conf

# Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.conf

# Various default settings
#Include conf/extra/httpd-default.conf

# Secure (SSL/TLS) connections
#Include conf/extra/httpd-ssl.conf
#
# Note: The following must must be present to support
# starting without SSL on platforms with no /dev/random equivalent
# but a statically compiled-in mod_ssl.
#
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>


Include "c:/wamp/apache2/conf/alias/phpmyadmin.conf"
Include "c:/wamp/apache2/conf/alias/sqlitemanager.conf"

------------------------------------------------------------------------------------------------------------------

My WAMPSERVER doesn't start APACHE when i uncomment that Virtual Host line
I' using WAmpServer Version 1.7.3.

Please if you could give Remote Assistance to get this working i been trying for a good week.

Thanks

Hi,

You are getting there. Replace the following lines in httpd.conf:

Order deny,allow
Deny from all
allow from 192.168.0.2
allow from 86.8.209.99

with these two lines:

Order allow,deny
allow from all

Do not use 'subdomains' of localhost, like dummy-host.localhost. The use of subdomain preceding localhost seems to utterly confuse the domain lookup in Windows.

Instead, add the following two lines to the hosts file c:\windows\system32\drivers\etc\hosts, to allow testing from the browser running on the WAMP server itself:

127.0.0.1 dummy-host
127.0.0.1 dummy-host2

Add the directory entries for each host:

<Directory c:/www/docs/dummy-host>
Options Indexes FollowSymLinks Includes
Order deny,allow
Deny from all
Allow from 127.0.0.1
</Directory>

Delete or modify your first virtual host which does not seem to be right - I am sure you do not own the domain getmyip.com.

Here is the file conf/extra/httpd-vhosts.conf you should try. Once you get that working from the browser running on your WAMP server, you can relax the security and change the line 'Allow from 127.0.0.1' something more permissive.

# ------------------
# httpd-vhosts.conf
# ------------------
NameVirtualHost *:80

<VirtualHost *:80>
ServerAdmin webmaster@dummy-host
DocumentRoot c:/www/docs/dummy-host
ServerName dummy-host
ErrorLog c:/wamp/logs/dummy-host-error_log
CustomLog c:/wamp/logs/dummy-host-access_log common
<Directory c:/www/docs/dummy-host>
Options Indexes FollowSymLinks Includes
Order deny,allow
Deny from all
Allow from 127.0.0.1
</Directory>
</VirtualHost>

<VirtualHost *:80>
ServerAdmin webmaster@dummy-host2
DocumentRoot c:/www/docs/dummy-host2
ServerName dummy-host2
ErrorLog c:/wamp/logs/dummy-host2-error_log
CustomLog c:/wamp/logs/dummy-host2-access_log common
<Directory c:/www/docs/dummy-host2>
Options Indexes FollowSymLinks Includes
Order deny,allow
Deny from all
Allow from 127.0.0.1
</Directory>
</VirtualHost>

Regards,



toivo
Sydney, Australia

Hi,

Thanks for all the help, i have resolved that problem :-).

Although i was woundering for security reasons in the file "C:\wamp\Apache2\conf\extra\httpd-vhosts.conf" i have "deny from all" and used the feature i.e. "allow from 90.128.00.20" so no random can access my server as i have no proper security for it, what could i do to increase the security? If i did allow eveyone what could hackers do? Would they be able to see my C: etc?

I have also tested the features on WAMP when i'm offline i have gave permissions to certain IP addresses, which can access my webpage as this works and when i use the feature to go online shouldn't everyone be able to access the webpage. As the ones that i have given access to are the only clients that can access it.

Is there anyway i could add to the config files when someonline goes to the server they are asked for a username and password or an registration for a login?

This would be a very secured and i would be appreciated if you would be able to help me?

You have been very helpful for eveything, very appreciated.

Thanks mate,
Mitesh

Hi,

Good that everything has worked out :-)

If you set up the folder for the virtual host correctly, Apache looks after the security so that the user will not be able to traverse above the document root.

If you have just static content, or HTML pages and files to be downloaded, there is not much hackers can do other than look at the HTML source code to find clues about other details of your site like subfolders, javascript folders and so on.

If you are planning to install an established Content Management System (CMS) like Joomla, that has its own security which sanitizes the HTTP request and removes common exploits from the request like attempts to set global variables and execute MySQL queries.

You need to be careful if you have written your own application and prompt for input. Do a search and read about 'SQL injection', for example at en.wikipedia.org/wiki/SQL_injection, and you will find a lot of things to consider.

There is a way to include usernames and passwords with folders, explained in [httpd.apache.org]. This requires one of the auth modules to be selected in the Apache modules option of the WAMP icon in the System Tray. If you do a search on '.htaccess username password', you will find a number of tutorials about login security on the web.

Regards,



toivo
Sydney, Australia

Hi,

Thanks alot for all the help,

As i going to be doing a project on an imlementation of football database very similar to "[news.bbc.co.uk];, as i have thought i could have some security for when updating database. I.e. results of matches, 2-1 for man utd vs chelsea.

I have still not started the implementation, i was just wondering what would be the best suggestion of how to be successful in doing this project. Would i update it from online? or striaght through MySQL.

Thanks for everything you been a star, mate,
Mitesh

Hi,

It would be best to have administration screens to prompt for data and store the results. They would be necessary to create and update all the lookup tables, to avoid costly mistakes if you try to do things directly on the database tables.

I have some source code at [totaldata.biz]. It is a structured, procedural (non-object oriented) set of code libraries and a sample application for a basic CRUD (Create Read Update Delete) framework for database updates.

If you are after productivity in programming and Rapid Development Tools, have a look at PHP on Trax at [phpontrax.com].

Regards,



Post Edited (10-31-07 11:10)

toivo
Sydney, Australia

Hi,

Yeah sure i will look into them, and i will try implementing that little section which i could add in to the project after.

As i have looked at your website i found the document "maintitem.zip", is that what you were on about? As this creates, reads, updates and deletes data.

Have you got any examples of how i would create an Administration Login Page?

By anychance do you use any messgers i.e. Yahoo Messenger, Msn Messenger etc. As if i do struggle in the future i can get some quality help of you. This would be very appreciated once again.

Thanks alot,
Mitesh



Post Edited (10-31-07 13:33)

HI,

There are plenty of tutorials and source code available from different support forums. If you are going to tackle a major developement, you should look at a CMS like Joomla, which comes with already tested security, hundreds of extensions and a developer community.

Regards,



toivo
Sydney, Australia

Hello mate,

I have bought a domain name from Godaddy and i would like to use it on the WAMP server. I have tried adding the address and the ip address on the domain name to the file "c:\windows\system32\drivers\etc\hosts" for some reason its not doing anything.

Please help,

Thanks.

ta5na wrote:

> Hello mate,
>
> I have bought a domain name from Godaddy and i would like to
> use it on the WAMP server. I have tried adding the address and
> the ip address on the domain name to the file
> "c:\windows\system32\drivers\etc\hosts" for some reason its not
> doing anything.

anything in your hosts file is only accessable to you. to get your domain name to work, follow the directions in my wamp manual.


CyberSpatium
----------------------
WAMP English Forum Admin

I have WAMP5 working with (for development use only):
Windows Vista Ultimate x64 (64 bit)
Kaspersky Internet Security Suite 7.0.x
Spyware Terminater 2.x
CounterSpy 2.5.x


Need help? Check out my WAMP User Manual/Guide here!


Web Development for Newbie's Blog - Check out my new blog. It is for web developers, and especially tailored for the web development newbie. If you are not fluent in “geek speak”, then this incredible resource is just you. And even if you are a web development pro, this is a great resource to check out some of the latest web development tips, news, tutorials, codes and more.

Hi,

The hosts file in the WAMP server is only used when the browser runs on the WAMP server itself and does a domain lookup. You can also add the same entry (consisting of the internal IP address of your WAMP server and the domain name) to the hosts file of another workstation on the same LAN, to access your site on the WAMP server.

You need to add your new domain name to your virtual host definition, and that virtual host should then respond to requests addressed to that domain, assuming that your domain record points to your current IP address:

ServerName www.example.com

If you have a static IP address from your ISP, everything is fine. You need to make sure that the name server of your DNS provider points your domain to your static IP address.

If your IP address is dynamic, you need to make sure your modem/router supports one of the dynamic IP address providers like no-ip.com or dyndns.org and setup an account with the provider, talk to your domain registrar and update the name server (NS) addresses in the domain records to point to the name servers of the dynamic IP service.

In addition to modem or router supporting dynamic IP address updates with a provider, the providers like no-ip.com have client applications you can run to update your IP address with the name server when the dynamic IP address changes.

Regards,



toivo
Sydney, Australia