RE: [squid-users] Squid 2.4.1+squidGuard and webdav support

I've done some further investigation to try and track this
problem down, setting up a small test environment with
Win2k Small Business server and a linux box running
squid 2.4.1+squidguard 1.2.0.

Upon trying to retrieve Exchange 2000 web access pages,
I keep getting messages like this in the log:

996157962.704 12 10.1.1.98 NONE/400 1626 NONE
error:unsupported-request-meth
od - NONE/- -

This happens whether I try to use squidguard to re-write
URLs on the way in, or just using squid as a normal caching proxy
(without squidguard), which is leading me to believe that
squid 2.4.1's webdav support does not provide everything that
Exchange 2000 requires...

Do the unstable/development versions of squid have more
complete webdav support?

Thanks in advance :)

Regards

Jethro Rose
System Administrator
Emerge Technologies Pty. Ltd.
jrose@emerge.net.au

-----Original Message-----
From: Rose, Jethro [mailto:Jethro.Rose@ofc.emerge.net.au]
Sent: Wednesday, 25 July 2001 10:25 AM
To: 'squid-users@squid-cache.org'
Subject: [squid-users] Squid 2.4.1+squidGuard and webdav support

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 Thu Jul 26 2001 - 01:13:21 MDT