PDF plugin repeatedly requests the same byte range for 64K of PDF data
Reported by
sote...@gmail.com,
Nov 6
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36 Steps to reproduce the problem: 1. We are not able to find out any reproducible test case. 2. 3. What is the expected behavior? Plugin should send reasonable number of requests to server. What went wrong? In some cases we see on server many the same repeated requests from plugin to server. It starts fine with normal requests but then it gets wrong. We do not know what causes this. We see many thousands of the same quickly repeated requests and of course it causes overload on server side. We have limited request history on server so I do not know when it started to happen. I see this problem with multiple plugin versions (we have many clients for which we provide out content as PDF with byte range support), some agent examples I can see, request is for 65536, we return 206 and when I checked on server requested byte range it was the same for given document. Some agents: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.79 Safari/537.36 Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36 Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.2454.0.47 EikonViewer/45.2454.0.47 Safari/537.36 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Edge/17.17134 Did this work before? N/A Chrome version: 70.0.3538.77 Channel: stable OS Version: 10.0 Flash Version: We are looking for some way to find cause of this behavior.
,
Nov 6
There was an issue around the Chrome 6x timeframe that we are aware of, but that should have been fixed. If some users have somehow stopped getting updates and are stuck on older versions, there is not much we can do to update them.
,
Nov 6
Please can you refer to fixed issue and let me know which version was this fixed in?
,
Nov 6
Bug 861550 . I think it was introduced in Chrome 67 and fixed in Chrome 69.
,
Nov 7
,
Nov 8
So far I did not see any such problem with version > 68 but I cannot say if it is because people do not use latest Chrome or if it is because Chrome 69 has it fixed. But I see normal range requests from 69 and 70 so I assume second variant is more probable. Give me about a week I will check again. Thanks.
,
Nov 8
Most users are on the latest stable version of Chrome, which is currently 70. You should be able to look at your server logs and verify this. I'm going to close this bug report since we can't do anything about users that cannot / refuse to update, and I do believe the bug has been fixed in the latest version. Please let us know if you do spot problems and we can reopen and investigate. On the server side, it may be possible to mitigate this by adding a rule so the server tells affected clients it does not support byte ranges. |
|||
►
Sign in to add a comment |
|||
Comment 1 by dtapu...@chromium.org
, Nov 6