Re: html files not named .html
montulli@stat1.cc.ukans.edu (Lou Montulli)
From: montulli@stat1.cc.ukans.edu (Lou Montulli)
Message-id: <9311162209.AA48904@stat1.cc.ukans.edu>
Subject: Re: html files not named .html
To: sanders@bsdi.com
Date: Tue, 16 Nov 93 16:08:58 CST
In-reply-to: <199311162130.PAA29310@austin.BSDI.COM>; from "Tony Sanders" at Nov 16, 93 3:30 pm
X-Mailer: ELM [version 2.3 PL2]
>
> Lou Montulli writes:
> > * 1) HTTP/1.0 servers should ALWAYS return a content-type tag!!!!!!!!!
> Rob McCool replies:
> > This has been fixed in the recent release... it will now return a default
> > type.
>
> I don't agree that servers should ALWAYS return a content-type:
> because there is a defined default if content-type is missing.
> http://info.cern.ch/hypertext/WWW/Protocols/HTTP/Body.html sez:
> The data (if any) sent with an HTTP request or reply is in a format
> and encoding defined by the object header fields, the default being
> "plain/text" type with "8bit" encoding.
> *However*, defensive programming would dictate that you be explicit.
This is what Lynx does. Unfortunatly since Xmosaic doesn't do that
I get complaint after complaint about how Lynx is screwed up because
it renders what they think is fine (because it works in Xmosaic)
into crap.
>
> Note that the HTTP/1.0 spec:
> http://info.cern.ch/hypertext/WWW/Protocols/HTTP/HTTP2.html
> has changed a bit over the past few months. Both server and browser
> authors should probably re-read it.
>
> --sanders
>
I did read it and look where it got me :)
(Perhaps the default should be changed since all of the Mosaic browsers
seem to default to text/HTML.)
:lou
--
**************************************************************************
* T H E U N I V E R S I T Y O F K A N S A S *
* Lou MONTULLI @ Ukanaix.cc.ukans.edu *
* Kuhub.cc.ukans.edu ACS Computing Services *
* 913/864-0436 Ukanvax.bitnet Lawrence, KS 66044 *
* UNIX! Cool! I know that! Jurassic Park - The Movie *
**************************************************************************