Odhiambo Washington wrote:
Hello gurus,
I have been trying the whole day to get Squid to work as a reverse
proxy/accelerator for OWA and RPC-over-https with no sucess. I believe
I've come to my /etc on this!
I have read the Wiki entries and this thread:
Henrik Nordstrom disse na ultima mensagem:
On lör, 2008-05-31 at 18:35 -0300, Michel (M) wrote:
hi
when running multiple squid instances squid cannot not resolv host names
from remote dns servers. It is necessary running named on localhost to
get
clear
the failing squid instances below
On Sun, Jun 1, 2008 at 1:38 PM, Amos Jeffries [EMAIL PROTECTED] wrote:
Odhiambo Washington wrote:
Hello gurus,
I have been trying the whole day to get Squid to work as a reverse
proxy/accelerator for OWA and RPC-over-https with no sucess. I believe
I've come to my /etc on this!
I have read
Can someone point me to how to encode the passwords using the helper?
On Sat, May 31, 2008 at 4:12 PM, Henrik Nordstrom
[EMAIL PROTECTED] wrote:
On fre, 2008-05-30 at 09:50 -0400, Chris Riggins wrote:
No, it is possible to use digest authentication to avoid
cleartext passwords. The squid wiki
On sön, 2008-06-01 at 13:23 -0700, Lawrence Anthony wrote:
Can someone point me to how to encode the passwords using the helper?
Here is one:
echo -n user:realm:password | md5sum
Using Apache htdigest is another..
Regards
Henrik
signature.asc
Description: This is a digitally signed message
On sön, 2008-06-01 at 09:45 -0300, Michel (M) wrote:
yes I understand the msgs but it is not the case, I run the exact same
config on the exact same machine (only by stopping 2.7 and starting 2.6
with the exact same configs) and 2.6 works but 2.7 does not
And they are built with the same
Odhiambo Washington wrote:
On Sun, Jun 1, 2008 at 1:38 PM, Amos Jeffries [EMAIL PROTECTED] wrote:
Odhiambo Washington wrote:
Hello gurus,
I have been trying the whole day to get Squid to work as a reverse
proxy/accelerator for OWA and RPC-over-https with no sucess. I believe
I've come to my
Hi all,
I am a (relatively) new squid administrator, and all is well, with one
exception. I cannot access a specific intranet site, which resides on
a non-standard port.
I will elaborate:
squid machine with Dansguardian is running on 1.2.3.4, running as a
transparent proxy. Everything internet
2008/6/1 Edward Dam [EMAIL PROTECTED]:
We have one intranet site: www.example.com
When a user points to www.example.com, that webpage/server redirects
them to http://www2.example.com:8098/login.aspx
The redirection is timing out. I've put port 8098 as one of the
Safe_ports in squid.conf,
I have now redirected the port, using the following command:
iptables -t nat -A PREROUTING -m tcp -p tcp --dport 8098 -j REDIRECT
--to-port 3128
It seems I am getting further, but now I get:
__
ERROR
The requested URL could not be retrieved
While
When a user points to www.example.com, that webpage/server redirects
this is an port 80 request
them to http://www2.example.com:8098/login.aspx
then, it should redirect to port 8098
So, I think , pls try below.
iptables -t nat -A PREROUTING -m tcp -p tcp -d www.example.com
--dport 80 -j
For a very light use... Even a single PC would experience
problems with squid 3.1 and TPROXY 4.1... I switched back
to 2.6.20.21+cttproxy and squid 2.6STAB-20 for a time
being.
On Friday 30 May 2008 09:05, Amos Jeffries wrote:
That is interesting to note, and part of where my
problem lies.
Thank you. I already have set the
http_port 3128 transparent
option in squid.conf. The problem persists, however
On Mon, Jun 2, 2008 at 1:17 PM, Indunil Jayasooriya [EMAIL PROTECTED] wrote:
When a user points to www.example.com, that webpage/server redirects
this is an port 80 request
I've cleared the rules, and then applied your recommended iptables command.
Unfortunately, it puts me right back to where I started. When the
www.example.com redirects to http://www2.example.com:8098/login.aspx,
it never gets there and times out.
The rule that I put in to forward port 8098
14 matches
Mail list logo
