Dear all,
I totally agree with Basile on the fact that Shweby is not replacing
Squid. I have tried to help in testing and debugging Squid ICAP but I
found it very hard to understand. As I had been working on the ICAP
protocol in my Intern in Nextenso (Alcatel), I have got some knowledge
in HTT
On 23 Jun 2003, David Nicklay wrote:
> I did a check on this, and squid seems to be dropping the Set-Cookie
> lines, but it doesn't otherwise.
Yes, this is indeed hardcoded in the Squid sources due to the original
Netscape Cookie specification where it is/was specified that caches must
not cache
On Monday 23 June 2003 21.30, David Nicklay wrote:
> Agreed. That was only a quick and dirty hack for some well known
> backend servers (in reverse proxy mode with accel_single_host on).
> I would like to find a clean way of doing this, or alternatively
> for Squid to recognize what the Cache-Co
I did a check on this, and squid seems to be dropping the Set-Cookie
lines, but it doesn't otherwise.
On Mon, 2003-06-23 at 15:37, Henrik Nordstrom wrote:
> On Monday 23 June 2003 21.20, Brian Akins wrote:
>
> > > Are you sure this is what you want?
> >
> > Yes. This is what we *need* to do.
>
On Mon, 2003-06-23 at 15:37, Henrik Nordstrom wrote:
> On Monday 23 June 2003 21.20, Brian Akins wrote:
>
> > > Are you sure this is what you want?
> >
> > Yes. This is what we *need* to do.
>
> Any you are aware this will in this specific example make Squid cache
> cookies?
>
Not if we drop
On Monday 23 June 2003 21.20, Brian Akins wrote:
> > Are you sure this is what you want?
>
> Yes. This is what we *need* to do.
Any you are aware this will in this specific example make Squid cache
cookies?
> If developers of backend apps refuse to not insert these headers
> they must be blind
On Mon, 2003-06-23 at 15:06, Henrik Nordstrom wrote:
> On Monday 23 June 2003 18.07, David Nicklay wrote:
> > to cache. In the process of debugging we found that this header
> > causes problems for squid:
> > Cache-Control: no-cache="set-cookie,set-cookie2"
>
> This looks like a reply-header, not
On Mon, 2003-06-23 at 15:06, Henrik Nordstrom wrote:
> > With a quick and dirty hack, I was able to make squid drop
> > the header and it subsequently was able to cache the request.
>
> Are you sure this is what you want?
Yes. This is what we *need* to do.
> This is obviously not acceptable in
On Monday 23 June 2003 18.07, David Nicklay wrote:
> to cache. In the process of debugging we found that this header
> causes problems for squid:
> Cache-Control: no-cache="set-cookie,set-cookie2"
This looks like a reply-header, not a response header.
There is no squid.conf tweaks to override rep
On Monday 23 June 2003 16.45, Basile STARYNKEVITCH wrote:
> Given that SquidIcap seems to be nearly dormant
It is not as dormant as it seems at a first look.
> I think that it is not a bad idea to have several "competing"
> ICAP client & HTTP proxy opensource implementations.
Fully agree on all
Hi,
While attempting to work with an unusual backend for our reverse squid
proxy, we came across a set of requests which squid refused to cache.
In the process of debugging we found that this header causes problems
for squid:
Cache-Control: no-cache="set-cookie,set-cookie2"
Squid will not cache t
> "Geetha" == Geetha Manjunath <[EMAIL PROTECTED]> writes:
>> On Friday 20 June 2003 01.00, Robert Collins wrote: > Duane
>> Wessels wrote: > > http://shweby.sourceforge.net/
>> > >
>> > > I find their logo interesting, especially since the
>> badmouth > > Squid in http://
Henrik Nordstrom wrote:
>
> I had fogot about this issue. I'll note this issue so it is not
> forgotten again. Needs to be fixed to not use MSG_PEEK so it can wait
> for more data to arrive via commSetSelect(), which involves some magic
> to get the interactions with the main Squid code correct.
mån 2003-06-23 klockan 14.17 skrev Geetha Manjunath:
> Yes, you are right here - but this case would probably show up only with
> buggy ICAP servers that do not end ICAP headers with \r\n\r\n . The rest
> of code catches this error. Actually it signals an HTTP internal error
> rather than the sugg
> I am keeping notes on found issues and
> shortcomings on http://devel.squid-cache.org/icap/
>
Thanks for the neat page, Henrik.
There is one more that was reported to me sometime back by Rui Ataide. I
haven;t confirmed this bug though. You may want to add it to the list .
" When ICAP is enable
Thanks for forwarding this, Henrik.
Hello Larry,
Sorry for this delayed reply..
> -Original Message-
> From: Rosenbaum, Larry M.
.
>
> 1) (icap.c) There is a problem with the way icapRespModReadReply()
> tries to read the ICAP header without reading past the header. The
>
Rather than building our test scripts up to be more and more complex,
I'm considering dropping a copy of cppunit (JUnit for C++) into squid.
CPPUnit doesn't use esoteric features AFAIK, and is known to work on
Visual C++ and g++.
Are there any objections to this? I'm happy to create a devel bra
Thanks. Applied.
Regards
Henrik
On Monday 23 June 2003 10.01, Reuben Farrelly wrote:
> Hi Henrik,
>
> A while ago we introduced the information line in squid that stated
> the type of connections being accepted, like this:
>
> 2003/06/23 19:14:49| Accepting transparently proxiedHTTP
> connectio
On Mon, 23 Jun 2003, Geetha Manjunath wrote:
> Should we start tracking squid-ICAP specific bugs for this ?? Any
> suggestions?
I am keeping notes on found issues and
shortcomings on http://devel.squid-cache.org/icap/
> BTW, how do you normally track bugs in squid? ... if any ;-)
For official
>
> On Friday 20 June 2003 01.00, Robert Collins wrote:
> > Duane Wessels wrote:
> > > http://shweby.sourceforge.net/
> > >
> > > I find their logo interesting, especially since the badmouth
> > > Squid in http://shweby.sourceforge.net/doc.php
> >
> > Yeah, that kindof sucks. Particularly as they
20 matches
Mail list logo
