Hi. I need advice on how to get webDAV working through my pound
inteface, if that is the correct terminology. First here is my
pound.cfg:


## global options:

User            www-data
Group           www-data
#RootJail       /chroot/pound

## allow PUT and DELETE also (by default only GET, POST and HEAD)?:
ExtendedHTTP    0

WebDAV          1

## Logging: (goes to syslog by default)
##      0       no logging
##      1       normal
##      2       extended
##      3       Apache-style (common log format)
LogLevel        1

## check backend every X secs:
Alive           30

## use hardware-accelleration card supported by openssl(1):
#SSLEngine      <hw>


######################################################################
## listen, redirect and ... to:

## redirect all requests on port 8888 ("ListenHTTP") to the local
webserver see "UrlGroup" below):
ListenHTTP 192.1.2.173,80

##
UrlGroup ".*"
BackEnd 127.0.0.1,8081,1
EndGroup

----------------------------
The file above gives me great access to my plone site running on the
same box as pound, with the backend specified as the local machine's
port 8081 (not accessible directly to outside world - thanks again for
everyone's help last Friday).  Pound is listening on the box's NIC card
on port 80. That all works 100%. Just to recap, in zope.conf you must
have the following to override the ip:     ip-address 127.0.0.1


Now I have set the WeDAV to 1, per instructions, and I also set the
following in my zope.conf:

  <webdav-source-server>
    # valid keys are "address" and "force-connection-close"
    #address 1980
    address 192.1.2.173:1980
    force-connection-close off
  </webdav-source-server>
#

With that, webdav works fine to plone, except that I once again have an
additional port open to the world. The address part is in effect
overriding the earlier ip-address for this one service, per the
zope.conf instruction.  

My QUESTION: Shouldn't I be able to somehow set pound to accept WebDAV
and pass these to the backend servers? In my case, I tried specifying
127.0.0.1:1980 but it did not work. I appeciate any ideas - thanks!  
Jamie
PS Note: I now know my internal lan ip range is using a bad range - am
looking into this :-)



Jamie T. Robe
Automation Team Leader
The Planning Commission
(813)272-5940