I have been checking out about IMDB videos and it seems like the
original requests cannot be cached from an unknown reason.
the store log shows:
1345335832.436 RELEASE -1 B174D16A30640884673D882B55B3594C 200
1334135877 1302715098-1 video/mp4 16586249/16586249 GET
On 20.08.2012 10:10, Eliezer Croitoru wrote:
I have been checking out about IMDB videos and it seems like the
original requests cannot be cached from an unknown reason.
the store log shows:
1345335832.436 RELEASE -1 B174D16A30640884673D882B55B3594C
200 1334135877 1302715098-1
On 8/20/2012 1:38 AM, Amos Jeffries wrote:
The is the file number/name where it is being stored. Since
this is an erased operation that is always the magic F value.
It is not 1-to-1 related to the object being cacheable. It just means
the object *currently* stored needs removing.
On 8/20/2012 2:37 AM, Eliezer Croitoru wrote:
On 8/20/2012 1:38 AM, Amos Jeffries wrote:
The is the file number/name where it is being stored. Since
this is an erased operation that is always the magic F value.
It is not 1-to-1 related to the object being cacheable. It just means
the
On 20.08.2012 11:37, Eliezer Croitoru wrote:
On 8/20/2012 1:38 AM, Amos Jeffries wrote:
The is the file number/name where it is being stored. Since
this is an erased operation that is always the magic F value.
It is not 1-to-1 related to the object being cacheable. It just
means
the
On 20.08.2012 12:22, Eliezer Croitoru wrote:
On 8/20/2012 2:37 AM, Eliezer Croitoru wrote:
On 8/20/2012 1:38 AM, Amos Jeffries wrote:
The is the file number/name where it is being stored.
Since
this is an erased operation that is always the magic F value.
It is not 1-to-1 related
On 8/20/2012 4:03 AM, Amos Jeffries wrote:
If you wish. It is a minor regression for the use-cases where traffic is
being fetched from sources other than ORIGINAL_DST. That content should
still be cacheable as it was before. It is done this way for now so that
swapping ORIGINAL_DST in for
On 8/20/2012 3:45 AM, Amos Jeffries wrote:
Two possibilities:
1) Did you bump up the maximum_object_size? default being 4MB and these
objects are ~16MB.
my limit is 200MB
2) They are dynamic objects without any Cache-Control or Expires header
to explicitly state the cacheability age. That
