Hi Amos and Henrik
Thank you for your reply.
I did the following tests:
snprintf(buf, 128, "Cache-Control: no-cache;");
//alsosnprintf(buf, 128, "Cache-Control: no-cache max-age=1 no-store;");
//alsosnprintf(buf, 128, "Cache-Control: no-cache, max-age=1,
no-store;");
//als
Hi Amos and Henrik
Thank you for your reply.
I did the following tests:
snprintf(buf, 128, "Cache-Control: no-cache;");
//alsosnprintf(buf, 128, "Cache-Control: no-cache max-age=1 no-store;");
//alsosnprintf(buf, 128, "Cache-Control: no-cache, max-age=1,
no-store;");
//als
Alex tells me that its time to release Squid-3 RC1. I plan to start
the process tonight. If all goes well it should be done and
announceable in 24-48 hours.
DW
On mån, 2007-10-01 at 09:28 +1300, Amos Jeffries wrote:
> Apparently "Expires: -1;" is invalid. Better to use an explicit timestamp,
> even if its Jan 1970, just to be sure that it works as expected.
-1 is invalid, which by specifications means expired in the past. See
RFC2616 14.21 Expires.
But
On sön, 2007-09-30 at 16:22 -0600, Alex Rousskov wrote:
> BTW, why not make every size-related variable a signed or unsigned
> int64_t? Is this a performance optimization issue?
To mainly to get a separation when something refers to in-memory data or
external data.
It's clearer in Squid-2 where
On Mon, 2007-10-01 at 00:11 +0200, Henrik Nordstrom wrote:
> On sön, 2007-09-30 at 15:43 -0600, Alex Rousskov wrote:
>
> > Should _all_ size_t uses in BodyPipe be replaced with uint64_t then?
>
> Anything that relates to the expected body content size to be
> transferred over the BodyPipe, but n
On sön, 2007-09-30 at 15:43 -0600, Alex Rousskov wrote:
> Should _all_ size_t uses in BodyPipe be replaced with uint64_t then?
Anything that relates to the expected body content size to be
transferred over the BodyPipe, but not buffer or passwed chunk sizes.
Regards
Henrik
signature.asc
Descri
On Sat, 2007-09-29 at 19:56 +0200, Henrik Nordstrom wrote:
> Forwarded Message
> From: Tsantilas Christos <[EMAIL PROTECTED]>
> To: Henrik Nordstrom <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Subject: Re: cvs commit: squid3/src HttpHeader.cc HttpHeaderTools.cc
> Store.h SwapDir
>
> Hi Amos
>
> Thank you for your reply. I believe this is good solution.
> But after I made the change below in my custom web page:
>
> snprintf(buf, 128, "X-Infection-Found: Type=0; Resolution=2;
> Threat=URL;");
> buf[127] = '\0';
> ci_request_add_xheader(req, buf);
> snprintf(buf, 128, "Cac
> Update of cvs.devel.squid-cache.org:/cvsroot/squid/squid3
>
> Modified Files:
> Tag: squid3-ipv6
> configure.in
> Log Message:
> Fix syntax error in nsaddr tests
>
Guido, that was a feature. :-p
It was meant to provide an autoconf arranged function-macro 'ABC(i)' that
allows the nsa
Hi Amos
Thank you for your reply. I believe this is good solution.
But after I made the change below in my custom web page:
snprintf(buf, 128, "X-Infection-Found: Type=0; Resolution=2; Threat=URL;");
buf[127] = '\0';
ci_request_add_xheader(req, buf);
snprintf(buf, 128, "Cache-Control:
cache-r
Hi Adrian,
Thank you for your reply.
I use Squid 3.0 pre7 and Squid 3.0 pre6
Cheers,
Forrest
Adrian Chadd wrote:
>
> On Sat, Sep 29, 2007, JXu wrote:
>>
>> Hi
>>
>> Please help me to understand the question described as below:
>>
>> I added a service in c-icap to block some URLs(for exam
JXu wrote:
Hi
Please help me to understand the question described as below:
I added a service in c-icap to block some URLs(for example, www.yahoo.com)
and I did it. It displays permission denied web page (designed by me) when
the user enters these URLs.
After I made www.yahoo.com available,
13 matches
Mail list logo
