Port 80 still blocked for @Home users?

[Thomas Mondoshawan Tate]

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

On Tue, Oct 16, 2001 at 10:15:13PM -0700, Digital Wokan wrote:
> While not an overly problematic thing memory and processor-wise for most
> "family" sites running on @Home subscriber systems, it does bring up the
> problem of linking to outside files such as images.  You end up with
> some browsers asking for permission to mix secure and non-secure content
> and others just outright refusing to display the non-secure items.

Since I'm going to be moving away from .az to .va and my ISP there is
questionable, one question comes to mind: do web browsers automaticially
attempt to connect to port 8080 implicitly? (ex: if I specify
http://tank.dyndns.org, will it try tank.dyndns.org:8080 after trying :80?)

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

--h31gzZEtNLTqOjlF
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

iD8DBQE7zRnRYp5mUsPGjjwRAvs5AJ9bctQ1WDNJaEQWwxodIWXbIjWRFgCfdPmg
by0xd6yfCItPHhmHCvcqST4=
=u6IG
-----END PGP SIGNATURE-----

--h31gzZEtNLTqOjlF--