Hi all,
I was just wondering if anyone had tried using squid with squidGuard as
a reverse proxy.
More to the point - has anyone tried using squidGuard as a reverse proxy for
a
Microsoft IIS Server running Exchange 2000 web access ;)
Currently, the set up I have been using is as follows:
Internet ---------> Linux firewall running squid 2.4.1 and squidguard
1.1.4
* Squid listens on port 80, and accepts connections to
URLs containing http://server.foo.com/exchange and
http://server.foo.com/exchweb (the 2 base URLs
Exchange
2k web access seem to use).
* Squidguard contains a fairly simple ruleset to
re-write http://server.foo.com/exchange to
http://10.x.y.z/exchange (win2k box's IP address).
Ditto for http://server.foo.com/exchweb
/
/
\/
Microsoft Win2000 Server running IIS and outlook 2000 web access
Theory is to not expose IIS, except for the subset of URLs required to make
Exchange web access work.
This setup has worked fairly well in the past using Windows NT 4.0 server,
Exchange 5.5, squid 2.2.x, and an older version of squidGuard.
With Exchange 2000, there is a problem where any dynamic content (for
example,
the user's inbox) does not get displayed. The rest of the page (graphics,
the frameset, etc) are displayed, which leads me to believe that the
URL rewriting and access lists are working fine.
Investigating this, it appears that Exchange 2000 web access requires
"webdav" support to work - hence upgrading to squid 2.4.1 for webdav
support.
It still doesn't work :)
I've had a look through squid.conf to try and find anything that looks like
webdav configuration, to no avail.
Anyone tried a similar setup? Is squid 2.4 webdav support "usable" yet?
Any common "gotchas" to look out for? :)
If anyone would like to see configuration files, let me know and I'll post
them..
Thanks in advance :)
Regards
Jethro Rose
System Administrator
Emerge Technologies Pty. Ltd.
jrose@emerge.net.au
Received on Tue Jul 24 2001 - 20:24:11 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:01:18 MST