Yes. For a range request, if it cannot be satisfied by cache, is just passed on to the origin server. This is because there is no good thing to do with the request as partial responses cannot be cached and (as noted) always fetching the source object is not a good thing.
This hasn't come up much before because people who were concerned about this issue had already written plugins for various reasons and adding a background fill was easy. One issue with doing a background fill is that you would need to check inside the range request response from the origin server to determine the size of the source object. Perhaps we could do that and use the background fill config values to determine whether to start a background fill. We would want a separate switch (separate values?) so this wasn't done even if normal background fills were enabled. > Unfortunately, those fixes doesn't help this. The problem is documented in > at least one bug, e.g. > https://issues.apache.org/jira/browse/TS-683 > Another option that I've been pondering, which is more suitable for large > contents I think, is to kick off background requests for the full objects. A > plugin that does something like:
