[NEXUS-29524] Fixes DMG files upload to Raw Repo with content type validation ON #92
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ry with content type validation ON
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes NEXUS-29524 failure of DMG files upload to Raw Repositories with Strict content type validation set ON.
This exception for DMG files comparing expected DMG file mime type with the detected mime type.
Tested upload with local Nexus3 installation.
Nexus3 issue fix NEXUS-29524.
NB:
Better solution would be to fix used Apache Tika component to detect mime type of OCX DMG files correctly. Related Apache Tika issue is TIKA-3590.