--lEGEL1/lMxI0MVQ2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Dec 05, 2001 at 12:48:35AM -0700, Rick Rosinski wrote:
> Are there any docs on changing the port to 81?  Others say it is a pain. =
=20
> WHy?  What are the consequences of changing the port?

Yep. Read the docs at http://www.apache.org. It's not so much of a pain,
really, just that people can't go to http://www.yourhost.com and see the
page -- they have to go to http://www.yourhost.com:81. The consequences are
that, since you're not using a standard port now, web browsers won't be able
to communicate with the webserver software. As such, to even view the page,
you have to specify the port in the URL (eg: http://www.yourhost.com:81).

All it takes (in Apache) is a change of the directive in httpd.conf that
reads as "Port 80" to read "Port 81".

--=20
Thomas "Mondoshawan" Tate
phoenix@psy.ed.asu.edu
http://tank.dyndns.org

--lEGEL1/lMxI0MVQ2
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8Dh5UYp5mUsPGjjwRAqH4AKCqxRwpagU8cZITYdyDm7X5ohgCuQCePQlZ
XzEklecB9DxoA0L3Z0AEJfk=
=VkUf
-----END PGP SIGNATURE-----

--lEGEL1/lMxI0MVQ2--