More commonly what is used is something called named virtual hosts and
SNI, or application routing. With named virtual hosts www.abc.com points
to a folder on your system and the web pages/application all run from
there. www.def.com will point to another folder. Both have the same
address, but by referring to them by name, apache (or nginx or iis) can
decide what web page/application to serve. Application routing is just a
variation of that. www.abc.com/app1 points to a folder, and
www.abc.com/app2 points to a different folder. That can be done by the
web server or the framework of the application you program in. I haven't
had to use odd or different ports for anything in a very long time.
Kevin Bucknum
Senior Programmer Analyst
MEDDATA/MEDTRON
Tel: 985-893-2550
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Booth Martin
Sent: Wednesday, November 2, 2016 6:11 PM
To: Midrange Systems Technical Discussion
Subject: Re: HTTP listening ports and URL questions
Thank you for explaining that in a way I could understand. I appreciate
it.
That pretty much means a landing page then? Or a complicated solution?
On 11/2/2016 3:19 PM, Kevin Bucknum wrote:
Let me rephrase that. The portion of DNS that web browsers use doesn't
contain port numbers. There are SRV records in DNS that can point to
ports, but only a few protocols will try and look for them.
Kevin Bucknum
Senior Programmer Analyst
MEDDATA/MEDTRON
Tel: 985-893-2550
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
midrange.com
