cacheable object dose not match

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

cacheable object dose not match

joseph
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: Thu, 08 Jun 2017 16:42:39 GMT
Content-Length: 1406
Server: Jetty(7.6.0.v20120127)
---------------------------------------

bad cached header file

accept-encodingHTTP/1.1 200 OK
Accept-Ranges: bytes
Content-Length: 158484
Last-Modified: Fri, 31 Mar 2017 23:01:45 GMT
Server: ATS
Vary: Accept-Encoding
Connection: keep-alive
Content-Type: video/mp2t
Cache-Control: public, max-age=604800
Access-Control-Allow-Origin: *
Access-Control-Expose-Headers: Content-Range, X-ATLAS-MARKERS
Timing-Allow-Origin: *
X-ATLAS-MARKERS: colodeb,cslrtt,rtt80_100ms,csbrtt,ar2,dist2000_3000km
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: cacheable object dose not match

Amos Jeffries
Administrator
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, just the Vary metadata since it is a string.


Amos

_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: cacheable object dose not match

joseph
>>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 accept-encoding should be befor status line ??
2 they should be  on one line  without  cr ??

so i need to know befor reporting bug tks
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: cacheable object dose not match

Amos Jeffries
Administrator
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 line  on one line also
>
> 1 accept-encoding should be befor status line ??
> 2 they should be  on one line  without  cr ??

The "accept-encoding" you see there is part of the metadata TLV for the
"Vary" header. The letter "H" is the actual start of the ASCII portion
of the file.


> so i need to know befor reporting bug tks

I suggest you investigate the file(s) with the squid-purge and/or
ufsdump tools. Both of those should be able to identify and validate the
UFS/AUFS/diskd cache file contents for you in an easier to read format -
such as displaying what the binary parts mean.

Amos

_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users
Loading...