-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/11/2014 5:02 a.m., Steve Hill wrote:
> I'm seeing a lot of this in both 3.4.6 and 3.4.9:
>
> 2014/11/18 15:08:48 kid1| assertion failed: DestinationIp.cc:60:
> "checklist->conn() && checklist->conn()->clientConnection != NULL"
>
> I've looked
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/11/2014 6:59 a.m., Frank wrote:
> Hi,
>
> Since upgrading from 3.1.22 to 3.4.8 I have been unable to get the
> transparent mode to accept my IP. I am seeing permission denied in
> the transaction when I do a packet dump. I have read the
> docu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/11/2014 4:39 p.m., Kendrick . wrote:
> I am using centos7 with a 3.4 squid package. I have tried a
> commercial and a couple user made url_rewrite_program items. They
> have all not ran properly. I had to disable selinux as it was not
> pla
I am using centos7 with a 3.4 squid package. I have tried a
commercial and a couple user made url_rewrite_program items. They
have all not ran properly. I had to disable selinux as it was not
playing nice with several things.
How does one go about trouble shooting what squid/url_rewrite_program
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/18/2014 12:09 AM, Eliezer Croitoru wrote:
> HTML version at: http://www1.ngtech.co.il/repo/release-3.4.9.html I
> am happy to release the new RPMs of squid 3.4.9 and 3.5.0.2 beta
> for Centos 6.6 64bit.
> All The Bests, Eliezer Croitoru
Addit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey Frank,
To understand the issue better I am missing couple things.
I filtered the squid.conf (which is a basic thing to do) and the
content can be seen here:
http://www1.ngtech.co.il/paste/1216/
It seems like you do not understand what and how.
th
On 19/11/14 01:39, Brendan Kearney wrote:
> i would suggest that if you use a pac/wpad solution, you look into
> pactester, which is a google summer of code project that executes pac
> files and provides output indicating what actions would be returned to
> the browser, given a URL.
couldn't agree
Spam detection software, running on the system "master.squid-cache.org",
has identified this incoming email as possible spam. The original
message has been attached to this so you can view it or label
similar future email. If you have any questions, see
@@CONTACT_ADDRESS@@ for details.
Content p
Thats because you have not set your local network to squid. You have
to allow your network range 66.159.32.0/24
2014-11-18 15:59 GMT-02:00 Frank :
> Hi,
>
> Since upgrading from 3.1.22 to 3.4.8 I have been unable to get the
> transparent mode
> to accept my IP. I am seeing permission den
Hi,
Since upgrading from 3.1.22 to 3.4.8 I have been unable to get the
transparent mode
to accept my IP. I am seeing permission denied in the transaction when
I do a packet dump.
I have read the documentation making changes for 3.4.8.
I even allowed everything and no go.
I also compi
I'm seeing a lot of this in both 3.4.6 and 3.4.9:
2014/11/18 15:08:48 kid1| assertion failed: DestinationIp.cc:60:
"checklist->conn() && checklist->conn()->clientConnection != NULL"
I've looked through Bugzilla and couldn't see anything regarding this -
is this a known bug?
--
- Steve Hill
On Tue, 2014-11-18 at 08:35 -0300, Carlos Defoe wrote:
> Well, you just wrote a load balancer in PHP, with a load balancing
> algorithm in it. It serves the same purpose as HAproxy (I don't really
> use HAproxy, so I don't know, but I use the F5 big-ip which is
> perfectly capable of testing Intern
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 19/11/2014 12:30 a.m., schinken wrote:
> Hi there,
>
> i'm currently trying to do authentication against LDAP and NCSA
> auth - but it looks like, the user is never checked against NCSA if
> auth against LDAP failed (because the user doesn't exist)
Well, you just wrote a load balancer in PHP, with a load balancing
algorithm in it. It serves the same purpose as HAproxy (I don't really
use HAproxy, so I don't know, but I use the F5 big-ip which is
perfectly capable of testing Internet links behind squid). In you
scheme, WPAD is being used to te
Hi there,
i'm currently trying to do authentication against LDAP and NCSA auth -
but it looks like, the user is never checked against NCSA if auth
against LDAP failed (because the user doesn't exist):
> auth_param basic program /usr/lib/squid3/basic_ldap_auth -R -b
> "dc=COMPANY,dc=int" -D sq...
thank you very much.
it's right
i apologize
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/WARNING-deny-mime-type-ACL-is-used-in-context-without-an-HTTP-response-Assuming-mismatch-tp4668430p4668444.html
Sent from the Squid - Users mailing list archive at Nab
16 matches
Mail list logo
