I've seen a couple of sites recently that
end .com:808/
Even if going to the .com it redirects to
..com:808
Anyone know what this is and why they do it?
TIA.

--
http://www.isthisyourcat.com

And lo, T.J. didst speak in alt.internet.search-engines,alt.www.webmaster:

HTTP traffic uses port 80 by default. However, you can specify a
different port by including the number after the domain name and a colon.
This is useful if, for instance, you'd like to have more than one server
running on the same machine, or if you have a specific reason for
disallowing port 80 traffic. There are probably other reasons I don't
know about

Grey

--
The technical axiom that nothing is impossible sinisterly implies the
pitfall corollary that nothing is ridiculous.
- http://www.greywyvern.com/orca#sear - Orca Search - PHP/MySQL site
search engine

On Thu, 16 Feb 2006 13:12:29 +0100, T.J. <no1@home.invalid> wrote:

Addresses are given this way when non-standard port number is used for
communication. Default port for http is 80, so the address
http://www.example.com is in fact equivalent to http://www.example.com:80.

The real question here is - why someone uses non-standard port.

The only reasonable reason I know is testing. Ocassionally when my host
does upgrades new version of the software - before going live - is visible
at some different port for testing.

No idea what other reasons are. Other than it 100k5 c001 that is

Best,
Borek
--
http://www.chembuddy.com
http://www.bpp.com.pl

Hi,

Borek napisa³(a):
You are right the most common reason is testing.

The other reason could be another HTTP server program at the same
machine. For example usually the 80 port is used by Apache (forgot about
all M$ buggy stuff such as IIS, please. Thanks in advance ;-) ).

I'm working on Java based systems and we are using Tomcat or Resin as
application servers. We need apache to be present at the same machine at
the same time.

To access to different pages throught different servers yuou would use
port number after domain name. Sometimes there are fwe instances of the
same Web server but thats usually for testing purposes as Borek already
wrote.

Tomek

BTW: In our systems Apache handles all requests and sends them to Tomcat
throught connector so you would never see the port after address. But
sometimes it could be reasonable to use Tomcat directly.

TomekK wrote:
Nothing wrong with IIS. Plus, the detault port for the other big Open
Source web server Tomcat is :8080. We have both running on our
production machines (IIS on 80, Tomcat on 8080).


So there you go. Tomcat defaults to 8080.

SpaceGirl wrote:

I would not disscuss it could cause religious war betwean M$ lovers and
haters and that it NTG ;-)

You are right. Resin has the same port as a default value. But the same
does not mean unchangable ;-)

Take Care
Tom

"SpaceGirl" <nothespacegirlspam@subhuman.net> wrote:

First time I see Tomcat being called a big open source webserver :-)

I run IIS on 8080 and Apache on 80 :-D

As do some proxy servers.

--
John isa Perl programmer: http://johnbokma.com/perl/perlprogrammer.html

Fox G Bar: http://johnbokma.com/firefox/google-...stomizing.html

In alt.internet.search-engines on Thursday 16 February 2006 13:33, Borek
wrote:

At my workpace we run an Intranet webserver on port 8080. This is because
another company has the IT contract and they refuse to hand out root access
(and root access or its M$ equivalent is needed to establish a server on
the so-called privileged ports 1 to 1024). I would not expect this to be an
issue for an _Internet_ server - in fact our corporate Internet servers all
use port 80.

Anyway, port 808 seems a strange choice - from my experience the de facto
non-privileged ports for webservers are 8080 and 8000, and to a lesser
extent 8008.