[HELP] Custom port forwarding / Web folder

[.PJ]

I have a question, I have wamp installed, and when you go home domain, port 80, it shows the default index folder for wamp

for this example, lets say when I load up www.myhomedomain.com (port 80) it loads up C:\wamp\www

Well I have another folder, within \www, so C:\wamp\www\junk

I want to make it that when someone comes to www.myhomedomain.com:1234 (a random port number, not random, just yet to be assigned) it shows them the stuff within C:\wamp\www\junk.

Does anyone know how to do this? Or am I going to have to switch to MS IIS?

Thanks,

PJ

[+BudMan MVC]

How to do in apache 1.3

http://httpd.apache.org/docs/1.3/vhosts/examples.html

http://httpd.apache.org/docs/1.3/vhosts/examples.html#port

Port-based vhosts

* Setup: The server machine has one IP address (111.22.33.44) which resolves to the name www.domain.tld. If we don't have the option to get another address or alias for our server we can use port-based vhosts if we need a virtual host with a different configuration.

Server configuration:

...

Listen 80

Listen 8080

ServerName www.domain.tld

DocumentRoot /www/domain

<VirtualHost 111.22.33.44:8080>

DocumentRoot /www/domain2

...

</VirtualHost>

A request to www.domain.tld on port 80 is served from the main server and a request to port 8080 is served from the virtual host.

Same info for version 2

http://httpd.apache.org/docs/2.0/vhosts/examples.html

This document attempts to answer the commonly-asked questions about setting up virtual hosts

Running different sites on different ports.

You have multiple domains going to the same IP and also want to serve multiple ports. By defining the ports in the "NameVirtualHost" tag, you can allow this to work. If you try using <VirtualHost name:port> without the NameVirtualHost name:port or you try to use the Listen directive, your configuration will not work.

Server configuration

Listen 80

Listen 8080

NameVirtualHost 172.20.30.40:80

NameVirtualHost 172.20.30.40:8080

<VirtualHost 172.20.30.40:80>

ServerName www.example1.com

DocumentRoot /www/domain-80

</VirtualHost>

<VirtualHost 172.20.30.40:8080>

ServerName www.example1.com

DocumentRoot /www/domain-8080

</VirtualHost>

<VirtualHost 172.20.30.40:80>

ServerName www.example2.org

DocumentRoot /www/otherdomain-80

</VirtualHost>

<VirtualHost 172.20.30.40:8080>

ServerName www.example2.org

DocumentRoot /www/otherdomain-8080

</VirtualHost>

You could also do with with host headers

http://httpd.apache.org/docs/2.0/vhosts/name-based.html

Name-based virtual hosting is usually simpler, since you need only configure your DNS server to map each hostname to the correct IP address and then configure the Apache HTTP Server to recognize the different hostnames. Name-based virtual hosting also eases the demand for scarce IP addresses. Therefore you should use name-based virtual hosting unless there is a specific reason to choose IP-based virtual hosting.

Its a lots easier for your users to remember www.something.tld vs www.something.tld:port

With the use of dynamic dns you can point many different domains at the same public IP.. depending on which domain used to access your public IP would determine with site was shown to the user.