ASP.NET ISAPI extension (aspnet_isapi.dll)
am 17.01.2008 01:32:00 von herman
QUESTION:
How do you protect and unprotect file extension using the ASP.NET ISAPI
extension (aspnet_isapi.dll)?
I have Edit Script Mappings in Internet Services Manager to protect certain
file types and it works but once I authenticate the file
does not download.
PROBLEM:
When a file is uploaded for a user to receive a file, I get the follow error
message "". I checked the IIS 6.0 status code for this
request and I get a code 200.
My custom application is dynamically creating applications under a website.
Example: I have TWO websiteS called Site1, and Site2.
I logon to site1 where I have a button that will dynamically gernerate an
application under site2 (ex: http://site2/app1 or http://site2/app2 etc).
These dynamically generated application will allow a user to send or receive
a file. I am using forms Authentication on both sites.
ENVIRONMENT:
Windows 2003 Enterprise Server R2
IIS 6.0
Security: Forms Authentication
Asp.Net 2.0
Re: ASP.NET ISAPI extension (aspnet_isapi.dll)
am 17.01.2008 02:32:27 von David Wang
On Jan 16, 4:32=A0pm, Herman wrote:
> QUESTION:
> How do you protect and unprotect file extension using the ASP.NET ISAPI
> extension (aspnet_isapi.dll)?
> I have Edit Script Mappings in Internet Services Manager to protect certai=
n
> file types and it works but once I authenticate the file
> does not download.
>
> PROBLEM:
> When a file is uploaded for a user to receive a file, I get the follow err=
or
> message "". =A0I checked the IIS 6.0 status code for this
> request and I get a code 200.
>
> My custom application is dynamically creating applications under a website=
.. =A0
> Example: =A0I have TWO websiteS called Site1, and Site2. =A0
> I logon to site1 where I have a button that will dynamically gernerate an
> application under site2 (ex:http://site2/app1orhttp://site2/app2etc).
> These dynamically generated application will allow a user to send or recei=
ve
> a file. =A0I am using forms Authentication on both sites.
>
> ENVIRONMENT:
> Windows 2003 Enterprise Server R2
> IIS 6.0
> Security: Forms Authentication
> Asp.Net 2.0
This sounds like a problem that you are supposed to figure out since
you are the one implementing custom authorization. You might want to
find a programming/development related forum for such questions. I
usually consult to answer such questions.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//