Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-11226

Better Strict Content Type Validation

Details

    • Story
    • Resolution: Unresolved
    • Major
    • None
    • 3.0.0
    • CMA, Repository

    Description

      Background
      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.

      Acceptance

      • 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

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              mprescott Michael Prescott
              Peter Lynch Peter Lynch
              NXRM - Mad Max
              Votes:
              2 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:

                tigCommentSecurity.panel-title