[NEXUS-11226] Better Strict Content Type Validation Created: 10/19/16  Updated: 01/15/19

Status: Ready to Groom
Project: Dev - Nexus Repo
Component/s: CMA
Affects Version/s: 3.0.0
Fix Version/s: None

Type: Story Priority: Major
Reporter: Michael Prescott Assignee: Unassigned
Resolution: Unresolved Votes: 2
Labels: supportant
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
fixes NEXUS-11712 RAR uploading fails - Detected conten... Closed
fixes NEXUS-13076 Nexus proxy of maven npanday exe arti... Closed
relates NEXUS-10243 Content type exception uploading tar ... Closed
is related to NEXUS-16252 disable mime type validation by defau... Open
is related to NEXUS-16306 JAR-artifacts that have been repackag... Closed
is related to NEXUS-18846 Cannot add custom MIME types for down... New
Last Updated By: Joe Tom
Date of First Response:
Epic Link: Content Type Validation


There are zillions of file types unknown to us, but as strict content type validation is on by default, we will (and do) reject many things customers use.


  • Refine strict content type validation so that it only rejects known mismatches (you said 'X', but it looks like 'Y'), and allows unknowns in (you said it's 'X'/nothing, but I'm not sure what it is)
  • Make it easy for customers to add content type overrides (e.g. for situations where they've made their own content types)
    • Presumably those overrides should be in sonatype-work

Generated at Sun Feb 17 19:02:27 UTC 2019 using JIRA 7.3.3#73014-sha1:d5be8da522213be2ca9ad7b043c51da6e4cc9754.