Download request refers to an invalid range.
Problem reported by vasanth - 7/27/2018 at 10:15 AM
Resolved
Hi,
 
When I download a document from my development machine it works fine. But when I download a document after deploying the application in server it gives me "Session expired" error. And when I check the stack trace it says "Download request refers to an invalid range."
 
I am using DocumentUltimate 4.1
 
- Vasanth

6 Replies

Reply to Thread
0
Cem Alacayir Replied
Employee Post

When using DocumentUltimate on Azure (or on other Cloud service or in multi-server environments), you need to make sure:

  1. Sessions are shared between instances.
     
  2. Document cache folder is shared between instances.
Please read the instructions here:
0
Anonymous Replied
When I view the file using document viewer. The Download request refers to an invalid range error is displayed.
I have included the cache path in Web.config too. I couldn't resolve it? I'm using Document Ultimate 4.6.5 version not on Azure environment.
Please help me. 
0
Cem Alacayir Replied
Employee Post
Please update to the latest. This will fix ""Download request refers to an invalid range" error hiding the actual error.

Version 4.9.5/4.9.6 - October 12, 2019
  • Fixed: When downloading document parts (http range), instead of the actual error, "Download request refers to an invalid range"error could be thrown. This could hide the actual error related to document caching.

0
Anonymous Replied
Thanks I will try it
0
Anonymous I Replied
Please help me with the below issue.

When I click the download button in the document viewer. The below error results only for one user, not for others.
Download request refers to an invalid range.
File size: 74436
Requested range : 0 to 52428800

But my actual file size is 60 KB only and in the cache folder, the SourceName file type is 0KB. Why this error is displayed and file size is different too? I'm able to download and view files of 70KB too.

Also, I'm using the updated version(4.9.5) of the document ultimate not the Azure environment. I have included the cache path on the Web.config. 

Further, I have a doubt, If 2 files with the same file name but different file sizes.
Will they share the same cache folder?



0
Cem Alacayir Replied
Employee Post
DocumentCache creates the unique ID according to file size, modified date and extension when you are loading the file from disk. So even if 2 files has the same identical name, it does not mean they are the same files and cached the same. It depends on the size, modified date and extension. 

However if you are using DocumentSource with a stream or bytes constructor, you are responsible for providing a unique ID for the document so you can differentiate the files because DocumentCache cannot know the details about your stream or bytes. If you provide same unique ID for 2 different files, then the cache keys will collide

the SourceName file type is 0KB
This is normal, that file is only for information purpose (it shows the original file name only).

Reply to Thread