250 users is not large for Squid. Any of the production releases should
be able to handle that many without causing much of a CPU bump on modern
hardware. I think you can start with one Squid process and expand to
more if you find it stressing the machines. More likely you will need
more DansGua
Hi!
WEB-server`s ntlm-authenticate doesnt work by squid-3. * . Why?
Gennadiy.
--
I have 2 IIS website with Integrated Windows Authentication.
Users access internet and these 2 websites by squid.
Access internet is ok, but can’t access these 2 websites.
I have tied v3.1 and v3.2 with default config, but the problem still there.
It seems squid cut off www-auth information.
An
On 22.02.2012 03:15, Steve Tatlow wrote:
Hi,
We are running squid as a transparent proxy, with dansguardian doing
the
content filtering. All traffic will be coming from localhost and no
authentication is required. Can someone tell me how I ensure there
are
enough squid processes to support
On 22/02/2012 03:21, Muhammad Yousuf Khan wrote:
i am using debian lenny with squid ver 2.7.stable3
i have a squid box and also want to allow NAT port 25 and 110 for
email send receive , along with the squid service.
Please help me.
Thanks
Hi Muhammad,
This is beyond the scope of the squid
i am using debian lenny with squid ver 2.7.stable3
i have a squid box and also want to allow NAT port 25 and 110 for
email send receive , along with the squid service.
Please help me.
Thanks
Hi,
We are running squid as a transparent proxy, with dansguardian doing the
content filtering. All traffic will be coming from localhost and no
authentication is required. Can someone tell me how I ensure there are
enough squid processes to support a large number of users (maybe 250
concurrent u
On Wed, Feb 22, 2012 at 01:29:33AM +1300, Amos Jeffries wrote:
> On 21/02/2012 11:21 p.m., Fried Wil wrote:
> >On Tue, Feb 21, 2012 at 12:26:11PM +1300, Amos Jeffries wrote:
> >I have this error on my access.log
> >1329819182.985 0 CLIENT_IP TCP_DENIED/302 340 GET
> >https://webmail.domain.foo
On 21/02/2012 11:21 p.m., Fried Wil wrote:
On Tue, Feb 21, 2012 at 12:26:11PM +1300, Amos Jeffries wrote:
I have this error on my access.log
1329819182.985 0 CLIENT_IP TCP_DENIED/302 340 GET
https://webmail.domain.foo/ - NONE/- text/html
1329819183.011 0 CLIENT_IP TCP_MISS/404 1530 GET
On Tue, Feb 21, 2012 at 12:26:11PM +1300, Amos Jeffries wrote:
> - Proper HTTP *redirect* using 3xx status messages should work fine.
> But Squid needs to be configured to handle both the before and after
> URL when received from the client. Exchange only needs to handle the
> "after" URI.
>
>
>
Hi Amos,
Thanks for your very good explaination.
I wanna to specify all i want to need :
https://webmail.domain.foo/ --> https://EXCHANGE_IP/owa/
https://webmail.domain.foo/owa/ --> https://EXCHANGE_IP/owa/
https://webmail.domain.foo/rpc/ --> https://EXCHANGE_IP/rpc/
https://webmail.domain.foo/
11 matches
Mail list logo
