W3C home > Mailing lists > Public > www-talk@w3.org > March to April 1995

Re: ANNOUNCE: NCSA X Mosaic 2.6b1 Released

From: <wmperry@spry.com>
Date: Fri, 7 Apr 95 06:51 PDT
Message-Id: <m0rxERH-00001SC@monolith>
To: frystyk@w3.org
Cc: Multiple recipients of list <www-talk@www10.w3.org>
Henrik Frystyk Nielsen writes:
> 
> > > o HTTP header User-Agent now uses a slightly different format, for
> > >   consistency with other platforms: 
> > >
> > >User-Agent: NCSA Mosaic/2.6b1 (X11;SunOS 4.1.3 sun4m) libwww/2.12 modified
> > >
> > 
> > Is it possible that this field will ever conform to the spec?  
> >    User-Agent: NCSA-X-Mosaic/2.6b1 SunOS/4.1.3 libwww/2.12-modified
> 
> Well, it's not far from it. Everything within '(' and ')' is to be
> considered a comment which is not part of the field, but is allowed. So
> what is left is the two phrases:
> 
> 	 NCSA Mosaic/2.6b1	and 	libwww/2.12 modified
> 
> Here the problem is that both contain a space which is not allowed in a
> token.
> 
> A User-Agent field like
> 
>  User-Agent: NCSA-Mosaic/2.6b1 (X11; SunOS 4.1.3 sun4m) libwww/2.12-modified
> 
> would be OK.

  I proposed to the HTTP working group that this be changed to something
like:

User-Agent: NCSA Mosaic/2.6b1 ; library=libwww/2.12 modified ;
            os=SunOS 4.1.3 sun4m ; windowsystem=X11R5 ;
            other-fun=here

  This follows in the tradition of MIME having information that modifies
the main value (text/html ; version=3.0) - the version of Mosaic is
considered to be the main value, and all the others are just slight
modifications.  This also doesn't break old log engines that had to deal
with the severely broken way that NCSA mosaic used before.

  A few people liked it, but seems to be an HTTP/1.1 issue.

-Bill P.
Received on Friday, 7 April 1995 10:20:40 UTC

This archive was generated by hypermail 2.4.0 : Monday, 20 January 2020 16:08:16 UTC