W3C home > Mailing lists > Public > www-tag@w3.org > June 2002

Bad practice: Overriding HTTP content-type with a URI reference

From: Tim Berners-Lee <timbl@w3.org>
Date: Fri, 14 Jun 2002 19:08:07 -0400
Cc: ph@w3.org
To: www-tag@w3.org
Message-Id: <96B57CFA-7FEB-11D6-ABAE-000393914268@w3.org>

In the last call working draft of SGRS,
a reference to another document can specify the content type of the 
destination object in a way that overrides any content-type provided by 
the HTTP server . The same was true  of (svg? smil?).  I understand that 
the intent was specifically to be able to reference a lot of existing 
data in legacy (probably unregistered) mime types.

This is obviously counter to the architecture, but meets a real need
in practice for servers which just can't be configured by the people
who publish on them.  This is fact a social/tools mess - if the
config files took local directory input then all would be well.

Maybe a compromise is to only allow the link to specify the
content-type when the server is FTP (or something else
with no content-type control) or the HTTP server returns
text/plain or octet-steam, which seem to be used for
"don't know" types.

It is of course consistent to indicate "the contents of this document 
expressed in whatever language but then reinterpreted as 
application/whatever" but in practice such references are kludges and 
would for example make the introduction of new versions of 
application/whatever more difficult.

Received on Friday, 14 June 2002 19:08:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:55:52 UTC