id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc,launchpad_bug 992,Store Content-Type as part of directory entries,jsgf,somebody,"Some apps, particularly using the webapi, will want to associate proper content types with files. Issue #947 proposes a complex scheme which ties metadata with the actual file object in some way. I propose in this issue a simpler scheme: 1. In the directory entry, have ""content-type"" and ""content-encoding"" entries in the normal metadata hash. 2. On http PUT, create a directory entry inheriting the content-type and -encoding from the PUT request (if present). If one or both are not present, then leave the entries absent. 3. On GET, use the content-type and -encoding from the metadata if present. Otherwise use the current scheme (guess the content type from the filename, defaulting to text/plain; no encoding). To fill this out, the command-line tools would need some option to do nothing (current behaviour), explicitly set the type and encoding, or guess based on extension, magic-number sniffing, etc. The content-type would be full content-type syntax with type/subtype and parameters.",enhancement,new,major,undecided,code,1.6.0,,metadata integrity,,