[gopher] Re: Problem with SiMpLeMaChInEs

[Chris <chris@xxxxxxxxxx>]

The original talk of port 70 actually goes back to mozilla and how when you 
search on jughead the browser shows for instance:
gopher://hal3000.cx:3000/7
but the page displayed is:
gopher://hal3000.cx
or if i was going to:
gopher://hal3000.cx:7080
it looked as if i was there but the page displayed was:
gopher://hal3000.cx
This led to discusion on mozillas board and here about port 70 and has been 
quite fully thrashed about by now.
For some reason when moz decided to fix then unfix and reimplement gopher they 
chose to only allow port 70 and further made all gopher requests go to port 70 
regardless of what port you typed in, this imo is worse than saying you can 
only use port 70.
C

On Wed, 01 Aug 2007 18:33:25 +0200
Mark <mark@xxxxxxx> wrote:

> brian@xxxxxxxxxxxxx wrote:
> > Also, the word "should" doesn't mandate compliance. It's a
> > recommendation.
> >   
> I agree; that's why it's called an RFC and not something else. :)
> 
> The port 70 discussion started because someone forwarded their port 70
> internet to a different port on LAN? My idea about this, is that it is
> never a good idea to run a service on a different internal port than
> it's external port. This because it's a definite way to show
> difficulties like the one being discussed now. A rather pointless
> discussion anyway, imho. :)
> 
> --Mark
> 
> 
> 


-- 
Join FSF as an Associate Member at:
<URL:http://member.fsf.org/join?referrer=3014>