Re: lynx-dev Lynx bug : automatic following of links?

[David Woolley]

I didn't really want 150+K of lynx trace, especially incorrectly
MIME coded.

> Content-Type: TEXT/PLAIN; charset=X-UNKNOWN; name="l.trc"
> Content-Transfer-Encoding: BASE64
> 
> TFlOWF9TSUdfRklMRSBzZXQgdG8gJy91L2V1L2h1L2hlY2tlLy5seW54c2ln
> Jw0KTG9hZGluZyBjZmcgZmlsZSAnL3Vzci9sb2NhbC9saWIvbHlueC5jZmcn

However, if you look carefully at this, you will see that the
web ring operators are aware of the & problem are using the
HTML 4 reccommended option of using ; instead of & as a field
delimiter in hand coded form type URLs (actually the examples
wouldn't be valid from a real form).  You can't arbitrarily
use ;, but server side form handling code is advised to
use it where URLs may be hand coded.

(There is a proper character set designation for unknown 8 bit
characters, but, in any case, base64 is always inappropriate for
predominantly English plain text.)