Addendum to post #1 in this thread.....
A web server directory structure looks like this (the physical paths
are shown in brackets):
http://www.site.com (C:\www\site)
http://www.site.com/sales (C:\www\site\sa les)
http://www.site.com/hr (C:\www\site\sa les\hr)
The "sales" virtual directory has a web.config file with the following
settings:
<httpHandlers >
<add verb="PUT, POST", path="index.asp x"
type="System.We b.UI.PageHandle rFactory"/>
</httpHandlers>
Now if the "hr" directory is accessed using the following URL
http://www.site.com/hr
the "hr" directory WILL NOT inherit the settings of the web.config file
which exists in the "sales" virtual directory because configuration
information is processed by virtual directories & not by physical
paths......OK.. ..that's fine....
But if the "hr" directory is accessed using the following URL
http://www.site.com/sales/hr
then the "hr" directory in this case WILL inherit the settings of the
web.config file that exists in the "sales" virtual directory, am I
right?
Please correct me if I am wrong
Arpan
Arpan wrote:
What exactly are configuration section handlers in a web.config file?
How would you define them & what for are they used in web.config files?
Is it a must for web.config files to have handlers?
An example of handlers in a web.config file would be highly
appreciated.
Thanks,
Arpan