From b12bad0ed96d2f7c293595202f3389e3db25de60 Mon Sep 17 00:00:00 2001 From: "Roy T. Fielding" Date: Wed, 13 May 2009 20:59:33 +0000 Subject: [PATCH] update comments and place in public domain git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@774530 13f79535-47bb-0310-9956-ffa450edef68 --- docs/conf/mime.types | 23 +++++++++++++---------- 1 file changed, 13 insertions(+), 10 deletions(-) diff --git a/docs/conf/mime.types b/docs/conf/mime.types index 85f00d198f..91151e2308 100644 --- a/docs/conf/mime.types +++ b/docs/conf/mime.types @@ -1,13 +1,16 @@ -# This is a comment. I love comments. - -# This file controls what Internet media types are sent to the client for -# given file extension(s). Sending the correct media type to the client -# is important so they know how to handle the content of the file. -# Extra types can either be added here or by using an AddType directive -# in your config files. For more information about Internet media types, -# please read RFC 2045, 2046, 2047, 2048, and 2077. The Internet media type -# registry is at . - +# This file maps Internet media types to unique file extension(s). +# Although created for httpd, this file is used by many software systems +# and has been placed in the public domain for unlimited redisribution. +# +# The table below contains both registered and (common) unregistered types. +# A type that has no unique extension can be ignored -- they are listed +# here to guide configurations toward known types and to make it easier to +# identify "new" types. File extensions are also commonly used to indicate +# content languages and encodings, so choose them carefully. +# +# Internet media types should be registered as described in RFC 4288. +# The registry is at . +# # MIME type Extensions application/activemessage application/andrew-inset ez -- 2.50.1