|
On 14/05/2012 19:36, Nuno J. Silva wrote: > On 2012-05-14, Zack Mayson wrote: > >> On 14/05/2012 17:07, Kim Holviala wrote: >>> On May 14, 2012, at 17:33 , Cameron Kaiser wrote: >>> >>>> For most servers, caps.txt will be just another file. Only >>>> Bucktooth and Gophernicus generate it by pseudoselector. The >>>> server has no idea who is fetching caps.txt and for what >>>> purpose. >>> >>> Actually.... The original poster was somewhat correct with >>> that assumption. I can now fairly reliably determine between >>> UMN gopher client, Overbite (the latest betas) and other gopher >>> clients. >> >> Any evidence to back it up? Like an extract from your caps file >> maybe.....? Requests caps.txt? -> Overbite beta Requests gopher+ >> information for /? -> UMN gopher otherwise -> some other client >> (including Overbite non-beta) >> >> But this is more of an issue with Overbite beta being the only >> client supporting the caps.txt approach ATM, and of UMN >> requesting gopher+ data *before* seeing a menu Which means you can only log certain clients! This disproves the claim that you can log /all/ clients via that sort of method (which is what the OP was claiming, AFAICT). |
_______________________________________________ Gopher-Project mailing list Gopher-Project@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project