Re: [squid-users] HTTP Cache General Question

Thank you for the information.

One more question:

We're looking at researching if it is possible to cache P2P data in an
HTTP Cache (purely research). What we have assumed is that if we were
to send an HTTP request to an IP address (a diff peer) (1.2.3.4) and
the header would have a URI that does not correlate with the IP
address that the Web Cache would store based on the URI in the header.
 This way if we sent to a diff peer (5.6.7.8) with the same URI in the
header, we'd get back the cached data.

I know this big assumption, and would change our approach if not true,
but it seems logical to be able to work this way. Do you know if
Squid works in this way?

We also think it'd be possible for the cache to take the HTTP header,
check to see if the URI is in the cache, and if not send the header to
the domain in the header.

Thank you again

Mark Schall
Michigan State University
CSE Graduate Student

On Wed, Oct 7, 2009 at 11:17 PM, Amos Jeffries <squid3_at_treenet.co.nz> wrote:
> On Wed, 7 Oct 2009 11:24:29 -0400, Mark Schall <schallm2_at_msu.edu> wrote:
>> Hi,
>>
>> My name is Mark Schall.  I am a Master student at Michigan State
>> University.  I am working with a group, trying to work with HTTP
>> caches.  We were wondering if, in general do HTTP caches work by
>> caching data based on the IP addresses or by the URI of the HTTP
>
> In general? I wont dare to guess. Too many ways to do it and too many
> different software caches using those ways.
>
> Squid in particular stores them by hash. Older versions used hash of URL.
> Newer 2.x use Hash of URL + some Vary: headers and stuff.
>
>> request.  It seems that using IP addresses would be the most secure
>> means of caching, but the URI seems logical for multiple server
>> websites.
>
> I assume by 'secure' you mean 'secure against data leaks'. There is nothing
> inherently secure about caching in the first place. The cache admin always
> has access to the cached data in intermediary traffic.
> What security there is in caching is built on a trust between cache admin
> and website admin. The website admin trusts that the cache admin will obey
> the CC headers. The cache admin trusts that the website admin will set the
> headers correctly (private) to protect sensitive information and also
> inform how often objects get replaced etc.
>
> Amos
>
>
Received on Thu Oct 08 2009 - 12:53:38 MDT