some times chunked, sometime not chunked   

Hi: 
Recently I am dealing with transfer-encoding:chunked programming.
Could some experts in this field here give me answers to the puzzles:

1 Now, my local time is CEST,when I use IE tools like httpwatch or fiddler 
to test "www.yahoo.com" in midnight of CEST, I can usually got 
"transfer-encoding: chunked"in response header;
   However, when tested at daytime CEST, I cannot got it displayed by 
httpwatch.
It seems so stange. Do anyone have same experience with me?
   
2 as Chunked are decided by the very moment the server beginning to send 
response. At that moment, if server can decide the content-length, it won't 
use
chunked transfer-encoding. and if at that moment, content-length can not be 
caculated, responses will be sent chunkedly.
Is it something related to web server workload?

Thanks in advance for any clew.
koroppo

date: Wed, 27 Aug 2008 06:13:01 -0700   author:   koroppo

RE: some times chunked, sometime not chunked   

I think I know the reason. It is due to cache proxy in company internal 
network.

"koroppo" wrote:

> Hi: 
> Recently I am dealing with transfer-encoding:chunked programming.
> Could some experts in this field here give me answers to the puzzles:
> 
> 1 Now, my local time is CEST,when I use IE tools like httpwatch or fiddler 
> to test "www.yahoo.com" in midnight of CEST, I can usually got 
> "transfer-encoding: chunked"in response header;
>    However, when tested at daytime CEST, I cannot got it displayed by 
> httpwatch.
> It seems so stange. Do anyone have same experience with me?
>    
> 2 as Chunked are decided by the very moment the server beginning to send 
> response. At that moment, if server can decide the content-length, it won't 
> use
> chunked transfer-encoding. and if at that moment, content-length can not be 
> caculated, responses will be sent chunkedly.
> Is it something related to web server workload?
> 
> Thanks in advance for any clew.
> koroppo

date: Tue, 2 Sep 2008 05:00:01 -0700   author:   koroppo