Amos,
The last client write and server read both happen at timestamp of
2014/10/08 21:58:17.
But client writes take place multiple time after the last server read
has been done, until the client range has been fulfilled.
Thanks,
Satish
On Tue, Oct 14, 2014 at 8:46 PM, Satish Thareja wrote:
> Hi
Hi Amos,
Transfer encoding is being used in the HTTp transaction.
The client range request and the content length were known form the headers.
Store log also confirms the content-length to be the same.
Out of 103262382 bytes sent from the server, the header size is 462
bytes, remaining is the obj
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/10/2014 1:16 a.m., Satish Thareja wrote:
> Hi Amos,
>
> The client is being served the content as per the range in the
> request headers. The object is cacheable and there are no other
> caches involved.
>
> The client requested range : 36798-1
Hi Amos,
The client is being served the content as per the range in the request headers.
The object is cacheable and there are no other caches involved.
The client requested range : 36798-103216128 (incorrect value in the last email)
Object length : 103701442
Squid seen bytes(from server): 103262
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/10/2014 12:20 a.m., Satish Thareja wrote:
> Hi,
>
> I trying to get a video cached wherein the client sends a range
> request for the video object(Range: bytes=36798-103701442) which
> gets converted to request without range(range_offset_limit
Hi,
I trying to get a video cached wherein the client sends a range
request for the video object(Range: bytes=36798-103701442) which gets
converted to request without range(range_offset_limit set to 10MB).
What I see, is after squid serves the client request and gets about
103262382 bytes of data
