[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]
-----BEGIN PGP SIGNED MESSAGE-----
On Thursday 29 January 2009 02:23, Cameron Kaiser wrote:
> That is a fascinating question. There is no <crlf> after it, so I would say
> print it as is, a one-byte binary file if you like.
Well, the idea of the question was rather "how to handle a dot-cr-lf line in a
document which has to be served by Gopher?" :-)
Say, we have a file like that:
There's a line which contains a single dot, followed by CR/LF chars... If I
would be a Gopher server, how would I handle that? If I send that as-is, then
there is a pretty big risk that the client will cut the file after that
"dot-CR/LF" line, thinking that it is the end of transmition...
Matjaž proposed to turn such line into "dot-space-CR/LF". Indeed, that's an
interesting solution, as it doesn't change anything visually for the end user,
and make sure that the gopher client won't be fooled...
You'll find my public OpenPGP key at gopher://gopher.viste-family.net/PGP
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
-----END PGP SIGNATURE-----