S
Sergey V
Hi,
I need to cover by custom authentication algorithm both ASP.NET and other
resources within the site.
FormsAuthentication covers only resources beeing handled by ASP.NET. Other
generic resources can be retrieved without beeing logged on.
I'm trying to configure the site to handle all resources via ASP.NET. Is it
possible?
My results are
a.. Things are working OK under .NET 2.0 Development Server (started from
Visual Studio 2005)
b.. Under local WinXP IIS - non-ASP.NET resources (like *.htm, *.html) are
not being authenticated.
Solved by adding ".*" extension mapping to ASP.NET
c.. Under WinSrv 2003 SP1 / IIS6 there are following problems
1.. .* - is not recognized as valid extension
2.. After mapping .htm to ASP.NET - .htm pages are not served anymore.
a.. Browser shows completely blank page
b.. HTTP Watch tracks ERROR_HTTP_INVALID_SERVER_RESPONSE error code,
response stream is empty
c.. IIS log on the server gives error code 200, i.e. OK
Any ideas to configure this correctly under WinSrv 2003?
Or probably there is some other better way to imlement custom authentication
instead of FormsAuthentication?
Best regards,
Sergey.
I need to cover by custom authentication algorithm both ASP.NET and other
resources within the site.
FormsAuthentication covers only resources beeing handled by ASP.NET. Other
generic resources can be retrieved without beeing logged on.
I'm trying to configure the site to handle all resources via ASP.NET. Is it
possible?
My results are
a.. Things are working OK under .NET 2.0 Development Server (started from
Visual Studio 2005)
b.. Under local WinXP IIS - non-ASP.NET resources (like *.htm, *.html) are
not being authenticated.
Solved by adding ".*" extension mapping to ASP.NET
c.. Under WinSrv 2003 SP1 / IIS6 there are following problems
1.. .* - is not recognized as valid extension
2.. After mapping .htm to ASP.NET - .htm pages are not served anymore.
a.. Browser shows completely blank page
b.. HTTP Watch tracks ERROR_HTTP_INVALID_SERVER_RESPONSE error code,
response stream is empty
c.. IIS log on the server gives error code 200, i.e. OK
Any ideas to configure this correctly under WinSrv 2003?
Or probably there is some other better way to imlement custom authentication
instead of FormsAuthentication?
Best regards,
Sergey.