Re: Proposal on removing Content Negotiation from http 1.1

Please don't try to justify my assertions.. It will only cloud the issue.

A Web crawl output of gopher+ sites would be real useful (especially
if it didn't report menus since most gopher+ servers can return gopher menus
as html)

> Daniel DuBois wrote:
> > 
> > (I don't know what Navigator does with/means by its
> > 'document encodings', but certianly if Navigator doesn't do the auto-charset
> > adjustment now, it will soon.  It's too trivial not to make that next step.)
> Netscape Navigator does look for "charset", but if it's omitted, we
> default to whatever the user has set in the "encoding" menu. We don't
> like having to present these confusing choices to the user, but the
> current Web infrastructure doesn't use "charset" at all (or very
> little).
> Erik

The TIS Network Security Products Group has moved!
voice: 301-527-9500 x123 fax: 301-527-0482
2277 Research Boulevard, 5th Floor, Rockville, MD 20850

Received on Wednesday, 24 January 1996 14:38:34 UTC