1
DocumentViewer shows wrong document
Problem reported by M.A. Beets - 10/31/2024 at 3:17 AM
Resolved
Hi,

This is the second time A customer has noticed that the viewer shows the wrong document. 
The error is so bad because it's shows the document of another organisation!

We working with version 7.1.5

any help please

1 Reply

Reply to Thread
0
Cem Alacayir Replied
Employee Post Marked As Resolution
From the docs:

For generating the cache key, to uniquely identify a document file, we use a string combination of file extension, file size and file date, this way cache collisions do not occur and we can reuse the cached file even if the file name before extension is changed (file1.docx and file2.docx have same cache key because it's still the same document according to file extension, file size and file date).

File providers like FileSystemFileProvider (a file on disk, on Amazon S3, on Azure) can provide file size and file date automatically however some file providers will not have this knowledge, e.g.StreamFileProvider, MemoryFileProvider (how could they know date modified of your data in a byte array or a stream?).

So for this purpose, these kind of providers have an additional property or constructor argument named DateModified and/or Size. You need to specify these to ensure you uniquely identify a document.


For MemoryFileProvider, the size is already known as it's in memory. If the size is really different than the cache key should also be different. Extension part of the file name is important, not the whole file name.


Reply to Thread