On Thu, 11 Oct 2001, Glenn McCorkle wrote: > You seem to have miss-typed the URL
Well Glenn, I got that URL by mousing over and observing the bottom bar of NS 3.04. Using NS 4.76 shows the same form. > Try this one after adding this line to mime.cfg > > gopher/9 PNG>BMP|$epng2bmp.exe -s -o $2 $1 Unfortunately, the gopher protocol isn't supported in Linux Arachne... :-/ > gopher://wizard.dyndns.org:70/9/I/Xgopher.png > ('/' was missing _____________ ^_) I think this is just how Arachne interprets it. If you want to see the actual output from the server, telnet to port 70 of wizard.dyndns.org and hit enter once connected. The logs are interesting too... though not as interesting as they could be if they recorded as much info as Apache does... right Sam? ;-) When you clicked gopher://wizard.dyndns.org:70/9I/Xgopher.png in DOS Arachne, the server logged this: pm3107.cisnet.com: Fri Oct 12 03:07:40 2001 (): No match for selector: 9I/Xgopher.png (logs are recorded in UTC, btw ;-) Later, when you separated the /9I/ into /9/I/: pm3107.cisnet.com: Fri Oct 12 03:22:00 2001 (/Xgopher.png): Sent binary: I/Xgopher.png pm3107.cisnet.com: Fri Oct 12 03:28:48 2001 (/Xgopher.png): Sent binary: I/Xgopher.png With Netscape, a request for /9I/: localhost: Sat Oct 13 12:29:44 2001 (/Xgopher.png): Sent binary: I/Xgopher.png I'm not sure whether /9I/ or /9/I/ is actually correct according to the protocol. So far the only thing that sticks in my mind was a statement somewhere that gopher URLS are "tricky." > New screen-cap > http://www.angelfire.com/id/glenndoom/gopher3.jpg Cool. :-) > To get it working in all cases. > It would require that your server send a different "content-type" for > each file extension. And then that we add a line for each of them to > mime.cfg The gn server is supposedly able to cater to web browsers as well as gopher clients. I still haven't gotten that far yet. (Fighting city hall, and an engine compartment "steam cleaned" by the radiator are eating up entirely too much of my time lately. :-/ Once a gopher server looks like a web server to web browsers, I wonder if it will also look like a web server to the ISP's firewall that keeps www requests out. > --- on server --- > bmp gopher/9/i/bmp > gif gopher/9/i/gif > jpg gopher/9/i/jpg > png gopher/9/i/png > _________________ More like this: 92500x60.gif (1.5K) I/2500x60.gif wizard.dyndns.org 70 image/gif gif gnlink 9Old Uptime Graph (600K) I/997967481.BMP wizard.dyndns.org 70 image/bmp bmp gnlink 9Xgopher screenshot (8K) I/Xgopher.png wizard.dyndns.org 70 image/png png gnlink Of course, the downfall of gopher might also be partly attributable to the relative ease with which http servers, mime types, and directories can be set up and used. Gopher menus are much more hassle. - Steve
