Support for User-Agent?
wmperry@indiana.edu (William M. Perry)
Errors-To: listmaster@www0.cern.ch
Date: Mon, 16 May 1994 22:12:26 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <m0q37u5-00005eC@monolith>
Errors-To: listmaster@www0.cern.ch
Reply-To: wmperry@indiana.edu
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: wmperry@indiana.edu (William M. Perry)
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: Support for User-Agent?
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
>>>>> "cjm" == Christopher J McRae <mcrae@ora.com> writes:
cjm> We need the User-Agent header for a number of reasons - most
cjm> particularly for remaining backwards-compatible with older clients
cjm> as the technology continues to develop. I don't believe that
cjm> Mosaic currently sends it, and I know that violaWWW does. What
cjm> about the other clients? Is there any will out there to add this
cjm> anytime soon?
Mosaic for X sends it, but in a totally broken way. According to the
spec, there should be at most two tokens on the line. Something like:
User-Agent: XMosaic/2.4; libwww/version#
Mosaic sends:
User-Agent: NCSA Mosaic for the X Window System/2.4; libwww/version#
Not exactly adherent. :) Easy enough to change though. mo-www.c needs to
change char*HTAppName = "Mosaic-X";
Emacs-w3, violaWWW, and lynx all send the correct User-Agent field.
cjm> By the way, 'Referer:' would be nice too.
Emacs-w3 and lynx are the only ones I know of that implement this
already.
-Bill P.