I have an odd issue with ATS.  I have ATS set up to revalidate against
the origin server every 3 minutes.  So far so good.  However, when I get
a Range header in ATS, if the resource isn't currently valid in ATS, it
goes back to the origin server, asks for the range, returns it, and
leaves the resource as invalidated.

Why doesn't it ask for the whole resource from the origin, cache the
response and compute the range itself (like it would do anyway if the
full resource was cached)?

(If it's a bug, pointers to the general area of the code I should look
at could cause a patch to come - if I can convince my boss to (finally)
have a crack at it)

  Issac

Reply via email to