If I create a .docx file using MS Word and run "file -i myfile.docx" on Linux, I'll get the correct MIME type returned.
If I look at its header, it shows the expected: 50 4B 03 04 14 00 06 00 08.
However, once I use io3.Save and ZipPartStore to save the file, running "file -i mynewfile.docx" on Linux will return "application/octet-stream".
If I look at its header, it shows this instead: 50 4B 03 04 14 00 08 08 08.
Is this expected? My problem is that I'm uploading the generated .docx file to a web-based API that verifies the MIME type. Their check (like my Linux test) returns the "application/octet-stream" which then rejects the .docx file as invalid/corrupt.
Has anyone else run into something similar with the generated .docx files from Docx4j?