2.7 warns
tis 2008-04-08 klockan 08:05 +1000 skrev Mark Nottingham:
> I think at least a warning in cache.log would be good, so people are
> aware of how often it happens, and can discover why a particular
> request is a miss.
>
>
> On 07/04/2008, at 6:52 PM, Adrian Chadd wrote:
> > On Mon,
I think at least a warning in cache.log would be good, so people are
aware of how often it happens, and can discover why a particular
request is a miss.
On 07/04/2008, at 6:52 PM, Adrian Chadd wrote:
On Mon, Apr 07, 2008, Henrik Nordstrom wrote:
I didn't test 2.6 today, but I know from ear
On Mon, Apr 07, 2008, Henrik Nordstrom wrote:
> I didn't test 2.6 today, but I know from earlier that it falls back on
> miss on large response headers.
>
> Testing again to be sure and indeed it does. And not even a warning in
> cache.log about it..
Cute. Ok. Can we now release Squid-2.7 ? :)
mån 2008-04-07 klockan 16:25 +0800 skrev Adrian Chadd:
> You've tested 2.6 too? I read the code as handling a HIT but just not parsing
> the reply and sending it back verbatim.
I didn't test 2.6 today, but I know from earlier that it falls back on
miss on large response headers.
Testing again to
On Mon, Apr 07, 2008, Henrik Nordstrom wrote:
> Running a test on 2.7 now to see how it actually behaves in the
> situation.. and it's fine. With the object in-memory is serves a cache
> hit, and with the object on disk we get a "swapin failure" and fallback
> on cache miss. Fully acceptable and n
mån 2008-04-07 klockan 16:01 +0800 skrev Adrian Chadd:
> I'm trying to avoid doing the much simpler solution and ignoring the rest -
> ie, just having a local buffer, reading the reply from the server-side into it
> until we have all the headers, and then just copying the first 4k out.
> Thats a po
