You don't have to use 443 or 80. You can use 8080 or 5691 or 10000 if you want. There are free dynamic DNS services out there where you can type in "mywebsite.com" and have it redirect to "mywebsite.com:8080" or "127.0.0.1:8080." You can then have it mask or cloak the web site name so they still see "mywebsite.com." Michael
Adam Melancon wrote: >Yes, but if i used 443 then everyone would have to type in https when >accessing the site. >This is for relatives to see pics of the baby, and I know most of them >will just type melancon.org and leave off the https:// > >On 5/2/05, michael dolan <[EMAIL PROTECTED]> wrote: > > >>It's actually been a few years since I've done it. I think it might be >>time to do it again. I just played around with it anyway, and when the >>Mb died in that computer I stopped.. I knew cox upped both down and >>upload speed, but I had a brain freeze. Sorry, I had an exam today. >>Michael >> >>Joey Kelly wrote: >> >> >> >>>On Monday May 2 2005 17:24, michael dolan spake: >>> >>> >>> >>> >>>>You can easily get around your ISP blocking port 80, but the upload >>>>speeds will kill you on a cable connection. >>>> >>>> >>>> >>>> >>>Right, you can always use port 443 (SSL). I disagree about the upload >>>bandwidth being a problem, however. Cox at this time gives you half a megabit >>>upstream, which is more than capable of handling a low-traffic site. We've >>>run nolug.org for at least 5 years on either DSL or cable, plus scads of >>>other domains as well. >>> >>> >>> >>>------------------------------------------------------------------------ >>> >>>_______________________________________________ >>>General mailing list >>>[email protected] >>>http://brlug.net/mailman/listinfo/general_brlug.net >>> >>> >>> >>> >>_______________________________________________ >>General mailing list >>[email protected] >>http://brlug.net/mailman/listinfo/general_brlug.net >> >> >> > > > >
