I was wondering if anyone had any experience with squid and OWA on
Exchange 2003 proxies.
My major hurtles are two in number.
1) forms based authentication mode turns on ssl on the exchange
server. Https connections fail because it does not like the test cert
we put on the exchange server.
On Wed, 29 Oct 2003, Jonathan Giles wrote:
> 1) forms based authentication mode turns on ssl on the exchange
> server. Https connections fail because it does not like the test cert
> we put on the exchange server. Is there any way to tell squid to
> ignore the problem with the ssl test cert
Thanks again for the help, Henrik.
I got squid3 to compile and install, now having trouble getting it to
work.
in squid.conf in ver. 3, these are the options I have made:
https_port 443 cert=/etc/openssl/cacert.pem
key=/etc/openssl/privkey.pem accel defaultsite=owa.clinedavis.com
cache_pe
On Thu, 30 Oct 2003, Jonathan Giles wrote:
> in squid.conf in ver. 3, these are the options I have made:
>
> https_port 443 cert=/etc/openssl/cacert.pem
> key=/etc/openssl/privkey.pem accel defaultsite=owa.clinedavis.com
>
> cache_peer owa.clinedavis.com parent 80 0 no-query front-end-https
Thanks again for the help Henrik.
Answers to your questions are below.
On Thursday, October 30, 2003, at 05:57 PM, Henrik Nordstrom wrote:
On Thu, 30 Oct 2003, Jonathan Giles wrote:
in squid.conf in ver. 3, these are the options I have made:
https_port 443 cert=/etc/openssl/cacert.pem
key=/
On Fri, 31 Oct 2003, Jonathan Giles wrote:
> 1067612977.854 22 10.1.16.100 TCP_MISS/400 262 GET
> https://owa.clinedavis.com/exchange -
> FIRST_UP_PARENT/owa.clinedavis.com text/html
>
> TCP_MISS means that the page wasn't in the cache, so I should just
> ignore it right?
Right.. but the
Henrik Nordstrom wrote:
On Fri, 31 Oct 2003, Jonathan Giles wrote:
1067612977.854 22 10.1.16.100 TCP_MISS/400 262 GET
https://owa.clinedavis.com/exchange -
FIRST_UP_PARENT/owa.clinedavis.com text/html
TCP_MISS means that the page wasn't in the cache, so I should just
ignore it right?
Ri
On Mon, 8 Mar 2004, Alan Lehman wrote:
> I am seeing this same problem with the following config. My OWA server listens for
> http connections on port 80. I want the clients
> to connect to squid with https on port 443.
For this you must use squid-3 configured to use origin server class
cache_p
Henrik Nordstrom wrote:
On Mon, 8 Mar 2004, Alan Lehman wrote:
I am seeing this same problem with the following config. My OWA server listens for http connections on port 80. I want the clients
to connect to squid with https on port 443.
For this you must use squid-3 configured to use origin s
Eric Kahklen wrote:
I just ran across your post. You are using Exchange 2003 correct?? Why
are you setting this up? security?? I have a how to I am setting up to
use with Exchange 2000.
Eric
Yes, it is Exchange 2003. I am doing it primarily for security. I would be interested in seeing your how
On Tue, 9 Mar 2004, Alan Lehman wrote:
> I tried cache_peer with and without 'originserver' :
> cache_peer w.x.y.z parent 80 0 no-query originserver front-end-https=on
>
> and got this result:
> 1078805391.337 3 65.26.58.221 TCP_MISS/401 402 GET
> https://owa.gbutler.com/exchange/ - FIRST_U
Henrik Nordstrom wrote:
On Tue, 9 Mar 2004, Alan Lehman wrote:
I tried cache_peer with and without 'originserver' :
cache_peer w.x.y.z parent 80 0 no-query originserver front-end-https=on
and got this result:
1078805391.337 3 65.26.58.221 TCP_MISS/401 402 GET
https://owa.gbutler.com/exchang
On Sat, 20 Mar 2004, Alan Lehman wrote:
> I am still not able to authenticate to Exchange. My client presents the
> userid/password dialog, but it refuses to grant access. I've tried IE6
> and Mozilla 1.6. It appears Exchange is not receiving the user
> credentials.
Have you told Squid to forw
Henrik Nordstrom wrote:
On Sat, 20 Mar 2004, Alan Lehman wrote:
I am still not able to authenticate to Exchange. My client presents the
userid/password dialog, but it refuses to grant access. I've tried IE6
and Mozilla 1.6. It appears Exchange is not receiving the user
credentials.
Have you
On Sun, 21 Mar 2004, Alan Lehman wrote:
> I tried 'login=pass' - no change. Any other ideas? I've experimented
> with the Exchange/IIS authentication setting. The results seem to be the
> same regardless of the setting. Should it be set for "basic"
> authentication only?
Basic needs to be enabled
On Sun, 21 Mar 2004, Alan Lehman wrote:
> I tried 'login=pass' - no change. Any other ideas? I've experimented
> with the Exchange/IIS authentication setting. The results seem to be
the
> same regardless of the setting. Should it be set for "basic"
> authentication only?
Basic needs to be enabled
On Mon, 22 Mar 2004, Alan Lehman wrote:
>
> It is. I have login=pass, and authentication = basic (only) on
> eggchange.
needs to be login=PASS (or login=PROXYPASS depending on your setup)
Regards
Henrik
Henrik Nordstrom wrote:
On Mon, 22 Mar 2004, Alan Lehman wrote:
It is. I have login=pass, and authentication = basic (only) on
eggchange.
needs to be login=PASS (or login=PROXYPASS depending on your setup)
Regards
Henrik
That works. Sorry to be so dense. Thanks for all your help.
18 matches
Mail list logo
