Date: Mon, 21 May 2001 09:07:03 -0700
From: "em@nuel" <em@nuel.ca>
To: gopher@complete.org
Subject: [gopher] Re: web->gopher
Message-ID: <20010521090703.C15451@siva.heatdeath.org>
Mail-Followup-To: "em@nuel" <em@nuel.ca>, gopher@complete.org
References: <200105211555.IAA10946@stockholm.ptloma.edu>
 <200105211557.IAA11512@stockholm.ptloma.edu>
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200105211557.IAA11512@stockholm.ptloma.edu>;
 from spectre@stockholm.ptloma.edu on Mon, May 21, 2001 at 08:57:16AM -0700
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org


> By the way, I just discovered a mail in my spam-filter from you about some
> problem with the World Gopher list. I fixed it and it seems to work now --
> sorry about that. Typo :-)

Excellent!

> *and* :-) One tiny suggestion -- maybe make it turn "GET /" selectors into
> real HTTP URLs?

I used to do that, but I removed it after deciding that it's contrary to
the spec.  My interpretation is that the 'h' type denotes an HTML
document stored on a gopher server.  According to the spec, selectors
have no meaning.  There's nothing stopping 'GET /whatever.html' from
being a selector for a gopher server, so turning it into an HTTP request
is incorrect.

I create web links by creating an HTML document on the gopher server
that redirects the user to the destination web site.  It works well with
everything.

I don't handle HTML documents correctly yet.  Web->gopher should go
through and re-write all the URLs so that relative links work.