Re: default return is "text/html"?

Rick Troth (troth@rice.edu)
Thu, 14 Jul 1994 10:05:00 -0500 (CDT)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Martijn Koster: "Re: pragma no-cache -- Can we make it more useful?"
Previous message: Ken Fox: "Re: pragma no-cache -- Can we make it more useful?"
In reply to: Garrett Arch Blythe: "Re: default return is "text/html"?"
Next in thread: Paul : "Re: default return is "text/html"?"

> I mean, come on. We are connecting to HTTP, "HyperText" Transfer
> Protocol, shouldn't the default be text/html?

Good point.

What this suggests, then, is that HyperTextTPDs should
*always* include a content-type header line. In other words,
the server should pin a default type (text/html) on all questionable objects.

I mean, come on. What's so hard about tacking on ".html"
to any file it serves-out? That's just one way to eliminate the
ambiguity. There are others.

Or (again) the clients could be "smarter", and upon seeing
"<html>" or even just "<head>" or any other SGML-ish strings,
decide, oh yeah, this *is* HTML, otherwise make it plain text.

> Garrett.

-- 
Rick Troth <troth@rice.edu>, Rice University, Information Systems

Next message: Martijn Koster: "Re: pragma no-cache -- Can we make it more useful?"
Previous message: Ken Fox: "Re: pragma no-cache -- Can we make it more useful?"
In reply to: Garrett Arch Blythe: "Re: default return is "text/html"?"
Next in thread: Paul : "Re: default return is "text/html"?"