Re: [squid-users] Error 401.2 with OWA

The SSL update includes support for this header when forwarding requests
to cache_peer servers.

You should be able to use your IIS/OWA server as a cache_peer I think,
but I have never tested this without the reverse-proxy extensions to
Squid <url:http://devel.squid-cache.org/rproxy/>

Note: The reverse-proxy extensions is currently only available for
"Squid-2.6" which unfortunately is not very stable at the moment (and it
is uncertain if there will be a Squid-2.6 release. focus is now on
Squid-3). Hope to have the most important reverse-proxy extensions
integrated into Squid-3, but the reverse-proxy extensions has not yet
been updated for Squid-3 due to lack of time.

The reverse-proxy extensions (and the SSL update) is developed for our
eMARA reverse-proxy product which works just fine with OWA in most
configurations. (plain-text authentication required)

Regards
Henrik

tis 2002-12-10 klockan 12.29 skrev Marcel Hauser:
> secondly..
>
> for the meantime i'll try doing the ssl stuff with squid while communitating
> with the owa server through normal port 80. Now i have the problem that the
> owa server doesn't know that i'am using ssl. I read that mail about the custom
> header for the ISA Server (knowledgebase article) ... how can i do that with
> squid ? adding that custom header to each request sent by squid to the owa
> server ?
>
> Thanks for the help
>
> Marcel
Received on Tue Dec 10 2002 - 04:49:34 MST