[
https://issues.apache.org/jira/browse/TIKA-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison updated TIKA-4177:
------------------------------
Description:
On TIKA-4176 and TIKA-4175 and earlier on TIKA-4082, we added detection of
DRM/IRM protected files. As a start, we threw an EncryptedDocumentException for
those files. I'm wondering if we should create a separate DRMProtectedException
that subclasses EncryptedDocumentException so that users can tell the
difference?
Or is the difference too insubstantial to add the burden of more complexity?
If we go down this road, do we need to differentiate IRM from DRM?
This proposal would only be for the 3.x branch because it would be a breaking
change.
was:
On TIKA-4176 and TIKA-4175 and earlier on TIKA-4082, we added detection of
DRM/IRM protected files. As a start, we threw an EncryptedDocumentException for
those files. I'm wondering if we should create a separate DRMProtectedException
that subclasses EncryptedDocumentException so that users can tell the
difference?
Or is the difference too insubstantial to add the burden of more complexity?
This proposal would only be for the 3.x branch because it would be a breaking
change.
> Throw DRMProtectedException for DRM protected files in 3.x
> ----------------------------------------------------------
>
> Key: TIKA-4177
> URL: https://issues.apache.org/jira/browse/TIKA-4177
> Project: Tika
> Issue Type: New Feature
> Reporter: Tim Allison
> Priority: Major
>
> On TIKA-4176 and TIKA-4175 and earlier on TIKA-4082, we added detection of
> DRM/IRM protected files. As a start, we threw an EncryptedDocumentException
> for those files. I'm wondering if we should create a separate
> DRMProtectedException that subclasses EncryptedDocumentException so that
> users can tell the difference?
> Or is the difference too insubstantial to add the burden of more complexity?
> If we go down this road, do we need to differentiate IRM from DRM?
> This proposal would only be for the 3.x branch because it would be a breaking
> change.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)