I think if the problem were that simple, then I would not be posting the
problem. <location only works if the file is mapped to IIS. The files cannot
be be mapped to IIS for external administrative reasons, reasons that go
beyond not having physical or remote control of the server.
I am wondering if other people have been responsible for securing
non-asp.net content that have needed to share the same credentials as the
asp.net application and have been faced with the above restrictments. And if
so whether they had come up with something that was useful..
<re****@community.nospam> wrote in message
news:e5**************@tk2msftngp13.phx.gbl...
A Dilemma that I keep being faced with is a scenario where I require
authentication on virtually everything. HTMl files, GIF files, XML files,
JavaScript files and etc. And I am constantly dealing with Administrators
who refuse to allow me to map items so that asp.net handles authentication
for it.
I am wondering is it possilbe to make ASP.NET handle the authentication
for documents such as .HTML/.gif/.xml/.js without having to manually have
access to the server and assigning all files to be handled by IIS?