DW:
- A fix for 'range_offset_limit'. Moved the range_offset_limit
check earlier in the client-side processing -- before the request
is determined to be a hit or miss, and before its forwarded.
- Extended the logic for determning when a range request should be
an uncachable miss due to range_offset_limit. If the request
would be a HIT on a PENDING object, we force a MISS if we can't
give the client the offset that it wants right away.
- Found it necessary to add request->flags.we_dont_do_ranges. The
flag is set by the client side, and read in the server side to
figure out if the Range header should be sent or not.