Re: [Lynx-dev] Gopher: "GET /" urls with query string

[Tobias Girstmair]

On Sun, Apr 28, 2019 at 08:50:26PM -0400, Thomas Dickey wrote:
> I'm not sure (without setting up a test so that I can read the trace, etc):

I have prepaired some simple test cases for you, just in case.

1. using the 'GET /' syntax from a gophermap -- fails:
   echo $'htest\tGET /?p=1245\tisticktoit.net\t80\n.'|nc -l 7070 &; lynx 
gopher://localhost:7070

2. using the 'GET /' syntax in a URL -- works:
   lynx 'gopher://isticktoit.net:80/hGET /?p=1245'

3. normal gopher selector with spaces -- works:
   echo $'0test\tselector with spaces\tlocalhost\t7071\n.'|nc -l 7070 &; lynx 
gopher://localhost:7070
   nc -l 7071 # in a second console to observe the selector

So the problem might actually be in the parsing of the gophermap.  
Interestingly, gopher selectors with spaces work fine.