<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 14/05/2012 19:36, Nuno J. Silva wrote:<br>
<span style="white-space: pre;">> On 2012-05-14, Zack Mayson
wrote:<br>
> <br>
>> On 14/05/2012 17:07, Kim Holviala wrote:<br>
>>> On May 14, 2012, at 17:33 , Cameron Kaiser wrote:<br>
>>> <br>
>>>> For most servers, caps.txt will be just another
file. Only<br>
>>>> Bucktooth and Gophernicus generate it by
pseudoselector. The<br>
>>>> server has no idea who is fetching caps.txt and
for what<br>
>>>> purpose.<br>
>>> <br>
>>> Actually.... The original poster was somewhat
correct with<br>
>>> that assumption. I can now fairly reliably
determine between<br>
>>> UMN gopher client, Overbite (the latest betas) and
other gopher<br>
>>> clients.<br>
>> <br>
>> Any evidence to back it up? Like an extract from your
caps file <br>
>> maybe.....? Requests caps.txt? -> Overbite beta
Requests gopher+<br>
>> information for /? -> UMN gopher otherwise ->
some other client<br>
>> (including Overbite non-beta)<br>
>> <br>
>> But this is more of an issue with Overbite beta being
the only<br>
>> client supporting the caps.txt approach ATM, and of UMN<br>
>> requesting gopher+ data *before* seeing a menu</span><br>
Which means you can only log certain clients! This disproves the
claim<br>
that you can log /all/ clients via that sort of method (which is
what<br>
the OP was claiming, AFAICT).<br>
<br>
</body>
</html>