Disable WebDAV just for one URL??

Hi Ken, thanks for answering. Sorry if I was short on details; it's
tough to figure out how much detail is enough, lest my questions
either don't get answered or I get buried in non-sequiters.

I set up a FP web site - let's call it family.sld.tld. That's just a
welcome page and a link to "Secure". Under that is another FP web
site in family.sld.tld/Secure. On that site I've removed the tick for
anonymous access and enabled basic authentication. I've given all the
family members AD accounts which they use to log in when prompted. In
the Secure folder are /all/ the web pages for the family web site,
mostly ASP and a few HTM. There is a folder named Documents under
Secure which, strictly under the control of web pages that use ASP
upload components, permit family members to upload files into.
Likewise, there's a (ASP) web page that lists the contents of the
Documents folder (with A HREF tags to permit downloading), and I never
enabled browse access on that folder so people aren't tempted to surf
through the structure unfettered.

1. Thanks for clarifying how FP works. That's a relief.

2. I don't have the write option ticked in the MMC for any of those
folders, but the Documents folder does have the ACL on it augmented to
permit write access (er, modify, execute, read, list, write) to the
group which encompasses the members of the family. That was necessary
to enable to ASP upload component to perform its duties without me
having to jump through hoops trying to make it run in another context
with elevated permissions.

I guess it's the ACL biting me in the ass then. Any more thoughts??


Thanks much,
Brad


On Fri, 13 Aug 2004 10:06:44 +1000, "Ken Schaefer"
<kenREMOVE.TakeThisOut@THISadOpenStatic.com> wrote:

 >Hi,
 >
 >How exactly are you publishing the documents, and how did you set it up?
 >
 >It's hard to answer some of your questions without knowing the answer above.
 >I will try to answer some of your questions below:
 >a) FPSE (Frontpage Server Extensions) do not require WebDAV (or use WebDAV)
 >for publishing. FPSE publishing is handled via an ISAPI filter
 >
 >b) Enabling WebDAV publishing invovles going into IIS Manager, and ticking
 >the "Write", and/or "Script Source Access" checkboxes on the "Home
 >Directory" tab
 >
 >c) To control WebDAV publishing permissions, you would use NTFS permissions.
 >To control FPSE publishing depends on what version of FPSE you are using.
 >FPSE 2002 has a Sharepoint Administration Site (or similar) link in your
 >Admin Tools folder. You can give different groups permissions to do
 >different things.
 >
 >Cheers
 >Ken
 >
 >Cheers
 >Ken
 >
 >
 >"Brad Berson" <userj.TakeThisOut@no.spam> wrote in message
 >news:nqpnh0pa2ubu8n7edmhgq7fqfcg6q7hdi2@4ax.com...
  >>I have set up a web site for my family, and there's a page where they
  >> can upload files to (and download files from) a specific subfolder on
  >> the web site called Documents. In order for them to be able to upload
  >> and delete files I had to give that group write permissions to the
  >> folder. So far, so good.
  >>
  >> Then I discovered that when opening a file from that folder via the
  >> web site link, then closing it, I was given the opportunity to save
  >> changes. Whoops! That's not quite what I was intending to offer.
  >>
  >> I'm assuming that's WebDAV giving everyone the opportunity to change
  >> each other's files, right?
  >>
  >> Can I disable WebDAV just for that URL (i.e.,
  >> family.sld.tld/secure/documents) without affecting all the other web
  >> sites running on that server?
  >>
  >> Does Frontpage rely on WebDAV? Can I disable WebDAV without screwing
  >> up my use of Frontpage? At this point I'm really not interested in
  >> whatever else WebDAV is offering, but then again I'd hate to disable
  >> WebDAV entirely and decide four months later that I /do/ have a use
  >> for it.
  >>
  >> Thanks for any advice,
  >> brad dot berson at rectaltronics dot com
  >>
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Disable WebDAV just for one URL??