Bug 57313 - The DefaultType directive has been removed
Summary: The DefaultType directive has been removed
Status: RESOLVED WONTFIX
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Core (show other bugs)
Version: 2.5-HEAD
Hardware: All All
: P2 normal with 3 votes (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-05 13:25 UTC by Jon Ribbens
Modified: 2020-03-03 17:54 UTC (History)
1 user (show)


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jon Ribbens 2014-12-05 13:25:26 UTC 
The DefaultType directive has been removed. This means that you can no longer set the default MIME type. The DefaultType directive should be added back again. The ForceType directive is not a substitute as it does not set the default MIME type, it sets an override MIME type.
Comment 1 Eric Covener 2016-05-16 14:38:36 UTC 
See the discussion at PR#13986
Comment 2 Jon Ribbens 2016-05-16 15:00:13 UTC 
OK I read through that 7-year comment thread; it has absolutely nothing to do with this PR except that it also mentions DefaultType. No one in that PR was asking for DefaultType to be removed, merely for it to be optional. Removing it completely is bizarre and removes important functionality, i.e. being able to explicitly set a default MIME type when you know that it is correct.
Comment 3 Jon Ribbens 2020-03-03 16:25:21 UTC 
Just found my own bug report again when I came up against the same problem 5 years later and it still hasn't been fixed...
Comment 4 Eric Covener 2020-03-03 16:31:26 UTC 
It's a design decision, I don't think it's returning. It can probably be emulated though:

Header set Content-Type foo/bar "expr=%{Content_Type} =~ /^$/"