The :0000 after a URL is a direction to a particular port.
In a standard installation, Apache listens on a particular port. Off the top of my head, I can't recall what number, but it doesn't hugely matter.
You can create a second instance of Apache and direct that to listen to an altogether different port. You might also set up a different server application to listen on yet another port.
For instance, there are a number of web-based server administration tools which come complete with their own reduced-instruction web server. This means that they can be hooked up to, say, www.yourdomain.com:8123. Anyone surfng to that port will arrive at the server app, not your Apache.
Or you might use it to have a separate Apache, configured either to allow more or less access than your normal Apache. This could be used to validate logins etc.
Basically, it gives you extra layers of felixibility.
To answer your question 2. I haven't tried it, but my guess would be thatyou could happily have two frames as you describe loading through different ports on your server.
If the bottom frame content is password protected, a password dialog will pop up. If you fail authentication, you will get a standard "Authorisation Required" message in the bottom frame, and the top will load normally.
The top frame will not know what username and password you typed into the bottom frame, unless the bottom frame passes these details to the top frame explicitly.
Hope this clarifies things for you.
Regards,
Jack healy
www.combustion.ie
Check out our Free HoHoHosting offer!
