problem: type/* content-types and HTTP/1.0

Marc Andreessen (marca@ncsa.uiuc.edu)
Fri, 1 Oct 93 00:51:25 -0500

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Charles Henrich: "New tag (or old?)"
Previous message: Dave_Raggett: "The new draft of HTML+"

The latest CERN server seems to not recognize that when a client says
it accepts "image/*" or the like that "image/gif" and "image/jpeg"
etc. are indeed accepted.

This doesn't seem to be explicitly spelled out one way or the other in
the HTTP/1.0 spec, but the mailcap spec makes it pretty explicit --
"If the subtype is specified as "*", it is intended to match all
subtypes of the named content-type."

I'd strongly encourage adoption of this methodology by HTTP/1.0 and
the servers, as it makes the user's life much easier and it makes it
possible for browsers to conform to RFC 1343.

Marc

Next message: Charles Henrich: "New tag (or old?)"
Previous message: Dave_Raggett: "The new draft of HTML+"