lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lynx-dev] Extend gopher client functionality to support URL scheme


From: Thomas Dickey
Subject: Re: [Lynx-dev] Extend gopher client functionality to support URL scheme
Date: Sat, 14 May 2016 19:28:13 -0400
User-agent: Mutt/1.5.21 (2010-09-15)

On Tue, May 10, 2016 at 07:39:59PM +0200, kaltheat wrote:
> Hi,
> 
> recently I realized that lynx' gopher client implementation does not cover 
> the (non-RFC) URL scheme[1,2]. This scheme is supported by Overbite Addon for 
> Firefox for instance and gives a smoother experience when surfing from gopher 
> oceans into http seas. You can test it using this[3] address. With lynx 
> you'll see an information page generated by the gopher server once the client 
> does not handle the URL scheme properly, with Overbite there is a seamless 
> transition.
> 
> Would you mind to extend lynx' gopher client?
> 
> Regards,
> kaltheat
> 
> [1] 
> http://gopher.quux.org:70/Archives/Mailing%20Lists/gopher/gopher.2002-02|/MBOX-MESSAGE/34
> [2] gopher://gopher.viste.fr/0/attic/RFCs/non-rfc/URL_gopher_links.txt
> [3] gopher://gopher.floodgap.com/hURL%3ahttp%3a//www.floodgap.com/

Currently this goes to a refresh page, which Lynx doesn't automatically proceed
past:

←←←→→→                      Bucktooth Redirect to URL: http://www.floodgap.com/→
   REFRESH(5 sec): http://www.floodgap.com/

   You  are  following a link from gopher to another URL or protocol. You
   will be automatically taken to the site shortly. If you don't get sent
   there, please click here to go to the site.

   The URL linked is:

   http://www.floodgap.com/
     _________________________________________________________________


    generated by bucktooth 0.2.9

I'll take a look at what's needed to make it handle the url (patches
are as usual welcome...)

-- 
Thomas E. Dickey <address@hidden>
http://invisible-island.net
ftp://invisible-island.net

Attachment: signature.asc
Description: Digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]