12-25-04 09:51 AM
No, that would be a NOP.
IIsWebFile that does not define anything "more" cannot override parent
settings -- thus, it uses the inherited settings. It's like what happens
when you set a File to remove all ACLs and inherit from parent -- the file
ACL doesn't define anything more and does not override parent settings --
thus, it uses the inherited settings.
Now, if the IIsWebFile had "AccessFlags = 0" then access to this URL will
not be allowed. Ditto with AuthFlags, ScriptMaps, HttpErrors, etc -- these
properties, if defined, would override the parent settings.
Basic logic:
1. IIS is a web server, which translates resource access requests between
two namespaces -- the URL namespace and the physical filesystem namespace
2. Various IIS configuration act on either the URL or physical filesystem
namespace. For example, the "Read" permission in IIS determines whether
"GET" is allowed, while the "Read" permission in NTFS determines whether the
file can be read at all. Clearly, for someone to be able to "retrieve" a
resource over HTTP, the resource must satisfy both Read permissions in IIS
and NTFS, no matter how many intervening extensibility layers transform the
action.
3. NTFS related configuration metadata is stored on the filesystem itself.
URL namespace configuration metadata is stored in the metabase.
The analog to IIsWebFile for URL namespace metadata is File ACL for NTFS
namespace metadata. In other words, suppose the parent vdir has "Read"
permission enabled, but you do not want it to apply to a particular
resource. You can do this by either
1. Removing "Read" permission for the IIsWebFile of that particular URL
namespace
2. Removing "Read" NTFS ACL for the remote authenticated user that is
reading the filesystem namespace corresponding to the URL namespace
Same thing works in NTFS -- suppose the parent directory has "Read"
permission enabled for a user, but you do not want that user to be able to
read a certain file. You do this by changing the File ACL of that specific
file to deny Read to that user.
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"George Hester" <hesterloli@hotmail.com> wrote in message
news:e88n$Af6EHA.1296@TK2MSFTNGP10.phx.gbl...
Well sure that helps immensely. So this in the metabase for a file name.ext
access will not be logged:
At key LM\W3SVC\1\root\name.ext
with value:
id: 1002
Name: KeyType
UT: Server
DT: String
Data: IISWebFile
the remaining empty?
--
George Hester
_________________________________
"Kristofer Gafvert" <kgafvert@NEWSilopia.com> wrote in message
news:#3HdpeY6EHA.3616@TK2MSFTNGP11.phx.gbl...
> Hello,
>
> Say that you have a file that you do not want to log the requests for. For
> this file, you set the DontLog property to True. This property has to be
> written somewhere (how else would IIS know that it shouldn't log
requests?),
> so this is written in the metabase.
>
> So that is the purpose, when you want to set IIS specific properties on a
> file basis. This information is written in the metabase. The file does not
> look any different on the file system.
>
> You can try it yourself if you want. In IIS Manager, right click a file
and
> click Properties. Then uncheck the check box for "Log Visits". This will
> write this file into the metabase as a IISWebFile.
>
> Hope this helps.
>
> --
> Regards,
> Kristofer Gafvert
> http://www.ilopia.com
>
>
> "George Hester" <hesterloli@hotmail.com> wrote in message
> news:%23gmfC%23X6EHA.1300@TK2MSFTNGP14.phx.gbl...
> I can find nothing about what it is at Microsoft's KB.
>
>
http://windows.microsoft.com/window...136t.htm?id=319
>
> What's its purpose? I have lots of files in my IIS Web Server and none of
> them have this set in the Metabase for them.
>
> --
> George Hester
> _________________________________
>
>
[ Post a follow-up to this message ]
| 
