IIS, Webdav, and URLScan Configuration Silliness
Wednesday, July 2nd, 2003So myself and a co-worker are attempting to setup and configure a Webdav server/directory. After much frustration in trying to get connected. I finally had an epiphany. My co-worker installed URLScan and had it configured so that things were relatively locked down.
google(URLScan), of which I have used very little, consists of a *.dll file and an *.ini file (for configuration). Its sole purpose is to analyze URL requests and allow or deny them based on the configuration settings identified in the *.ini file. I believe its an add-on application of sorts for IIS that Microsoft released. Its purpose (I think) is to help server administrators lock down the wide variety of openings IIS leaves available, but for some reason doesn’t provide the control for natively through the IIS Manager interface.
We were running into problems trying to transfer files over via Webdav from both Windows and Apple based systems that have native Webdav support. The server logs should have been the first place I looked, but …. alas it was not. When I finally started looking at the server logs and URLScan’s log, I realized that key google(Webdav verbs) were being denied by URLScan. A simple modification of the *.ini file to allow those *verbs* needed by Webdav to pass through was all it took to start sharing/publishing files through a familiar network drive type interface.
Now that I have the base level thing working, I need to get access rights figured out (I only want specific users to have access to specific folders).