https://bz.apache.org/bugzilla/show_bug.cgi?id=57593
Vasili <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID |--- --- Comment #5 from Vasili <[email protected]> --- Look, how it behaves... >java -jar tika-app-1.7.jar --detect 096113YE06.xlsm application/x-tika-ooxml-protected but after I open and immediately close the file in Excel (neither changing anything nor changing the file type), it becomes normal (from the point of view of tika and POI) >java -jar tika-app-1.7.jar --detect 096113YE06_just_resaved.xlsm application/vnd.ms-excel.sheet.macroenabled.12 After the re-saving HSSF api works as for thousands of other files derived from the same template. So, users of the template, during filling it, probably encrypted it (as I guess) and then decrypted. And the file remained in some volatile temp state which was automatically fixed by the re-saving. I'm wondering whether you can detect the file correctly from HSSF by other means (not raising the Exception, I guess BIFF8 may exist even in the 1st case - if it's not the Office which adds it). Is it possible? Thanks -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
