i get the following error
[EMAIL PROTECTED] ~]# /usr/lib/squid/squid_ldap_auth -b
"ou=people,dc=cbsl,dc=lk"
-f "uid=%s" -d
gayanku cbsl
user filter 'uid=gayanku', searchbase 'ou=people,dc=cbsl,dc=lk'
squid_ldap_auth: ../../../libraries/libldap/search.c:189: ldap_search:
Assertion `ld != ((void
Rafal Ramocki wrote:
Amos Jeffries wrote:
Hello,
I have problem with my squid setup. For quite long time I've been using
Squid 2.6 STABLE-17. I decidet to switch to squid 3.0 but there is
problem.
My configuration is:
large network -> nat router (linux) -> router (hardware ATM) -> internet
Adrian,
On Mon, Mar 10, 2008 at 5:44 AM, Adrian Chadd <[EMAIL PROTECTED]> wrote:
> Hm, it doens't do this already?
nope, at least not in a way I would expect it to.
> Well, it certainly wouldn't be difficult to. File a bugzilla report;
> see if it tickles the fancy of anyone.
Did it. Will see
Adrian Chadd ha scritto:
Hi everyone,
As part of last years site redesign I had an idea for organising a "library" of
relevant papers, example deployment cases and anything of general interest.
Its a bit .. lacking. :)
You can find the two brief entries that I have there at
http://www.squid-cac
The http_access should look like this:
http_access allow msnmessenger msnURL
The two separate lines mean that you allow all kind of connections to
the listed domains and you also allow all connections that have
gateway.dll in the url (non msnURL sites too).
For example you can browse msn.co
The main logic in a nutshell:
acl: elements are ORed (be it a single line, multiple line or file)
http_access: a single line's acl elements are ANDed and if matched, you
get a final allow or deny depending what your line says. If there is no
match, check goes to the next line.
In your case:
> Am 2008-02-13 10:25:32, schrieb Matus UHLAR - fantomas:
> > by using the same URI? or by different URI each time a song is requested?
> > each of this makes problems with HTTP caching...
On 14.02.08 09:58, Michelle Konzack wrote:
> Yes, it is always the same url...
>
> For example: The origina
Amos Jeffries pisze:
Rafal Ramocki wrote:
Amos Jeffries wrote:
Hello,
I have problem with my squid setup. For quite long time I've been using
Squid 2.6 STABLE-17. I decidet to switch to squid 3.0 but there is
problem.
My configuration is:
large network -> nat router (linux) -> router (hardwa
Hello,
I've upgraded my squid 2.6 STABLE18 Squid 3 on FreeBSD 7.0.
Apparently, the http_acccess are not processed in proper order anymore
in Squid 3.
I have a couple of acls:
acl PROXYUSERS proxy_auth REQUIRED
acl XYZ dst XXX.YYY.AAA.BBB
acl FREE src "/squid/etc/IPS.free" # IPs that shouldn't
I have squid 2.6stable18 on a debian sarge box in non-transparent mode. I also
have apache web server setup on this box and it works fine - when the browser
is
pre-configured for the proxy.
I have some people come in and use their laptops from time to time so I need a
way to automatically dire
This is the problem that CARP and other consistent hashing approaches
are supposed to solve. Unfortunately, the Squid in the front will
often be a bottleneck...
Cheers,
On 07/03/2008, at 1:43 PM, Siu Kin LAM wrote:
Hi Pablo
Actually, it is my case.
The URL-hash is helpful to reduce the d
I'm curious to see what others have done for redundant/failover squid servers,
and any configs that go with it. If we run a squid server in branch offices and
it "dies" it would cause an outage and we would have to repair or build a new
one. Whats a good plan for going redundant?
The Squid HTTP Proxy team is pleased to announce the
availability of the Squid-3.0.STABLE2 release!
This release solves several problems in the earlier STABLE1
release and adds a few more features found useful in 2.6.
Please refer to the release notes at
http://www.squid-cache.org/Versions/v3/3.
Hi All,
I have configuration/compilation issues trying to set up squid with auth
using basic scheme and LDAP server.
1. I configured the squid make system with --enable-ssl=yes
--enable-auth=basic --enable-basic-auth-helpers=LDAP options.
2. I now try to execute make all and I get
Le Monday 10 March 2008 16:30:42 Nick Duda, vous avez écrit :
> I'm curious to see what others have done for redundant/failover squid
> servers, and any configs that go with it. If we run a squid server in
> branch offices and it "dies" it would cause an outage and we would have to
> repair or buil
[EMAIL PROTECTED] wrote:
I have squid 2.6stable18 on a debian sarge box in non-transparent mode. I also
have apache web server setup on this box and it works fine - when the browser is
pre-configured for the proxy.
I have some people come in and use their laptops from time to time so I need a
Amos,
While I appreciate the input on my config file, do you see anything that would
cause it to give me these errors?
Here is my wpad.dat:
function FindProxyForURL(url,host) {
return "PROXY 192.168.1.1:3128";
}
Here is what I see in the logs:
1205192406.411 0 192.168.1.99 TCP_
F5 has some documents on how to implement consisent hashes in bigip
irules (tcl),
but i wound up writing a custom one for use in front of our squids
that only does one
checksum per request, as opposed to one per squid in the pool, to avoid wasting
cpu cycles on the LB.
it uses a precomputed table
Thanks, Alex -- that's actually quite helpful.
It might be good to have a *little* more process around how ones
sponsors changes in Squid -- whether -2 or -3 -- to assure that
there's coordination between the feature sets, and that the entire
Squid developer community is bought into the cha
Hi,
I am a complete Squid newb with my first install done only yesterday,
2.6 stable(18). Can someone please help with basic ACL config for
network IP's, I would like to allow my local network and restrict just
one or two hosts by IP address. I have Googled a little but as there are
so many ACL co
You want to restrict one of your local IPs from getting on the internet?
Something like this:
acl LAN_Range src192.168.1.0/24
acl No_Internet_For_You src192.168.1.X (replace the X with the
IP you want to block).
http_access deny No_Internet_For_You
http_access all
> Amos,
>
> While I appreciate the input on my config file, do you see anything that
> would cause it to give me these errors?
>
> Here is my wpad.dat:
>
> function FindProxyForURL(url,host) {
> return "PROXY 192.168.1.1:3128";
> }
Okay. That makes it a problem with the request the brows
http://192.168.1.1/wpad.dat
IE6
-- Original message --
From: "Amos Jeffries" <[EMAIL PROTECTED]>
> > Amos,
> >
> > While I appreciate the input on my config file, do you see anything that
> > would cause it to give me these errors?
> >
> > Here is my wpad.dat:
> >
> F5 has some documents on how to implement consisent hashes in bigip
> irules (tcl),
> but i wound up writing a custom one for use in front of our squids
> that only does one
> checksum per request, as opposed to one per squid in the pool, to avoid
> wasting
> cpu cycles on the LB.
>
> it uses a p
So let me get this straight:
* Squid listens on 192.168.1.1:3128
* Apache listens on 192.168.1.1:80
* When IE is _configured_ for startup to load http://192.168.1.1/wpad.dat
* IE for a URI (any URI?!) it sends a request squid can't handle.
Next thing to check is that HTTP/1.1 is disabled in
On Tue, 2008-03-11 at 10:57 +1100, Mark Nottingham wrote:
> It might be good to have a *little* more process around how ones
> sponsors changes in Squid -- whether -2 or -3 -- to assure that
> there's coordination between the feature sets, and that the entire
> Squid developer community is b
On Mon, Mar 10, 2008, Alex Rousskov wrote:
> > WRT responsible sponsoring: I'm willing to pay a (reasonable) premium
> > to get the things that I pay to get into -2 into -3 as well,
>
> Thank you, and I am sure many sponsors would do the same if the
> trade-offs are explained to them correctly.
2008/3/11 Neil Harkins <[EMAIL PROTECTED]>:
> F5 has some documents on how to implement consisent hashes in bigip
> irules (tcl),
> but i wound up writing a custom one for use in front of our squids
> that only does one
> checksum per request, as opposed to one per squid in the pool, to avoid
I'll come back to one of Mark's earlier points then which seems to have
been lost. What will decide on adoption of -2 or -3 is the "killer app".
Developers roadmaps or sponsors notwithstanding. I think the point was
raised that neither roadmap was especially compelling or seemed to yet
contain
29 matches
Mail list logo
