Complete.Org: Mailing Lists: Archives: gopher: January 2009:
[gopher] Re: How to handle lines beginning by a dot?

[gopher] Re: How to handle lines beginning by a dot?

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: gopher@xxxxxxxxxxxx
Subject: [gopher] Re: How to handle lines beginning by a dot?
From: Mateusz Viste <mateusz@xxxxxxxxxxxxxxxx>
Date: Wed, 28 Jan 2009 22:49:57 +0100
Reply-to: gopher@xxxxxxxxxxxx

Hash: SHA1

On Wednesday 28 January 2009 22:29, Matjaž Mešnjak wrote:
> clients will terminate the connection when they find <cr><lf>.<cr><lf> (at
> least WSGopher and my Gopher Client). The line ".Blah!" can be sent without
> modifications.

That what I think, too... But then I do not understant why the RFC tells us 
that "Lines beginning with periods must be prepended with an extra period"... 
Have I missed something?

> If the text file contains "<cr><lf>.<cr><lf>" mail client would transform it
> to "<cr><lf>..<cr><lf>", but that's not the case with gopher. For text files
> you could modify it to "<cr><lf>.<space><cr><lf>"

That's a good idea, indeed. I have added that to my todo list for the next 
version of my gopher server :-)

> The problem could
> be with binary files that contain "<cr><lf>.<cr><lf>" - but the clients that
> I tried, downloaded the binary file correctly when it was sent as raw data -
> without "<cr><lf>.<cr><lf>" on the end.

That's rather normal - binary data has no "<cr><lf>.<cr><lf>" terminator, it 
just listens until the connection is closed by the server, so I would say that 
there's no surprise there...
By the way, I noticed that some Gopher clients (at least Firefox and Lynx) are 
displaying the "dot terminator" of text files just as it would be part of the 
document. Too bad for them :)

Best regard,
Mateusz Viste
- -- 
You'll find my public OpenPGP key at
Version: GnuPG v2.0.9 (GNU/Linux)


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