Invalid XOD file: Zip end header data is wrong size!

[David Compton]

We get the following error when files are loaded in our application on a frequent, intermittent basis.  All files are in xod format.   Given that it is intermittent I don't think that the problem is with our file server, although I'm not ruling that out.  Sometimes the error only appears in the browser console and does not stop the document from loading.  Other times it appears as an error in the web viewer itself, which is particularly bad as the end user then has to select another document or reload the browser to get rid of the error.

Invalid XOD file: Zip end header data is wrong size!

    at Object.onError (CoreControls.js:1123)

    at CoreControls.js:1130

You can see the problem if you go to https://app.docsontap.com.au and use the trial option.  If you have the browser console open and select different documents then you should find the error appears soon enough.  The error appears to happen more often if you just refresh the browser after having already viewed a document.

I've read other posts on this issue and none of them seem to resolve the problem.  Do you have any suggestions?  I'm happy to post the code for our file server - it is just a simple http server written in node - if that helps.

Kind regards,

David

[Zhijie Zhang]

Hi David,

Hope you are doing well.

Please check out the FAQ about this error if you haven't already: https://www.pdftron.com/documentation/web/faq/loading-errors#invalid-xod-file:-zip-end-header-data-is-wrong-size

WebViewer will try to fetch parts of a XOD document instead of the whole document at once for the purpose of performance. In your website, WebViewer is sending a range request with 22 bytes to https://app.docsontap.com.au/assets/files/TapHereToBeginPortrait.xod but the content-length of the response is 27792. 

This usually means your node server doesn't support HTTP range requests properly. As the FAQ suggests, one way to workaround this issue is to pass streaming: true to the WebViewer constructor function. However, this will hurt performance a bit so it'd be better if we can make the server support range requests. Please let us know if you want us to take a look at your server code.

Best Regards,

Zhijie Zhang

Software Developer

PDFTron Systems Inc.

[David Compton]

Hi Zhijie,

Your response put me on the right track.  That file you were referring to is the initial default document that we show.  It is stored locally on the device.  All other files are served from our file server, unless the user is offline.  So I needed to start off with streaming: true, and then change it to false once we load a file from the server.  I think the problem was intermittent due to timing issues.

Thanks for your help,

David

--
You received this message because you are subscribed to the Google Groups "PDFTron WebViewer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pdfnet-webview...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pdfnet-webviewer/c790eb32-ad13-4f0c-9bee-f59a50cc088c%40googlegroups.com.

--

David Compton

david.w...@gmail.com

[Zhijie Zhang]

Hi David,

Just to confirm that you managed to resolve the issue?

To load a file with streaming false you can do instance.loadDocument('file_path', { streaming: false });

Let me know if you have any other questions. Thanks!

[David Compton]

Yes the issue seems to be resolved.  Thanks again for your help.

--
You received this message because you are subscribed to the Google Groups "PDFTron WebViewer" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pdfnet-webview...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/pdfnet-webviewer/4395a8fc-3a9b-41aa-88cb-f505639f3da4%40googlegroups.com.

--

David Compton

david.w...@gmail.com