Re: Enhancement proposition: metadata for content-types

From: Daniel Stenberg <>
Date: Thu, 2 Sep 1999 08:36:00 +0200 (MET DST)
Message-ID: <Pine.GSO.4.10.9909020831520.8577-100000_at_jinx>

On Wed, 1 Sep 1999 wrote:

> One of the problems with the MIME attachments is how to make the web
> server send back their content type.
> One solution could be to add a file extension, but that extension is
> server dependent.

One problem with trusting the mail content is that instead of getting a "server dependent" type, we get a client dependent type. I have more than once seen people mailing attachments with the wrong content-type. But I guess we have to live with some kind of limitation.

> Another solution is to use meta-data to store the Content-Type header
> associated with each MIME attachment.

I like the idea.

> I implemented this version on my working version of hypermail and am
> succesfully using it against Apache (which supports metadata files). I'm
> unaware if other web servers, besides Apache and CERN (obsolete) support
> metadata.

Using the attachmentlink feature, you could easily write a CGI script that uses the meta data and the saved file, if the web server doesn't support it. It could work similar to this:


 echo "$meta_content_type";
 echo ""
 cat $the_attached_file

 Daniel Stenberg --
 You'll find my hypermail pages at
Received on Fri 03 Sep 1999 09:56:32 PM GMT

This archive was generated by hypermail 2.2.0 : Thu 22 Feb 2007 07:33:51 PM GMT GMT