Sakurai/pdf.js
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Use Content-Range instead of Content-Length #5512

Browse Source 
Use Content-Range header instead of Content-Length when the
response has status code 206, to work around issue #5512,
which is caused by a bug in Chrome (since version 39):
https://code.google.com/p/chromium/issues/detail?id=442318
This commit is contained in:
Rob Wu 2014-12-30 16:48:17 +01:00
parent 6e66e30d92
commit c02b2cb37c
1 changed files with 16 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
src/core/worker.js
View File

@ -106,6 +106,22 @@ var WorkerMessageHandler = PDFJS.WorkerMessageHandler = {
var length = fullRequestXhr.getResponseHeader('Content-Length');
length = parseInt(length, 10);
//#if (GENERIC || CHROME)
if (fullRequestXhr.status === 206) {
// Since Chrome 39, there exists a bug where cached responses are
// served with status code 206 for non-range requests.
// Content-Length does not specify the total size of the resource
// when the status code is 206 (see RFC 2616, section 14.16).
// In this case, extract the file size from the Content-Range
// header, which is defined to be "bytes start-end/length" for
// byte range requests.
// See https://github.com/mozilla/pdf.js/issues/5512 and
// https://code.google.com/p/chromium/issues/detail?id=442318
length = fullRequestXhr.getResponseHeader('Content-Range');
length = length && /bytes \d+-\d+\/(\d+)/.exec(length);
length = length && parseInt(length[1], 10);
}
//#endif
if (!isInt(length)) {
return;
}