On 14/06/17 02:11, joseph wrote:
No. The cache file contains a TLV structure of metadata followed by the
right but so it should be a TLV bindery and after that ?? HTTP/1.1 200 OK
wish is text clear or anything betwean thim as this -->>
accept-encodingHTTP/1.1 200 OK
accept-encoding and status
>>No. The cache file contains a TLV structure of metadata followed by the
right but so it should be a TLV bindery and after that ?? HTTP/1.1 200 OK
wish is text clear or anything betwean thim as this -->>
accept-encodingHTTP/1.1 200 OK
accept-encoding and status line on one line also
1 ac
On 14/06/17 01:35, joseph wrote:
if you open the hex cached file
first header or so should be HTTP/1.1 200 OK
right ???
No. The cache file contains a TLV structure of metadata followed by the
response 'on-wire' syntax.
You appear not to be able to see (or cut-n-paste) the binary TLV
prefixes,
if you open the hex cached file
first header or so should be HTTP/1.1 200 OK
right ???
is this correct in one line will be cacheable hit or corrupted
accept-encodingHTTP/1.1 200 OK ???
good cache header file example
HTTP/1.1 200 OK
Via: cache-yes
Content-Type: image/x-icon
Last-Modified
