webclient.downloadfile

[jared]

I've been toying with an asp.net diretory browser and have been trying to
use system.net.webclient.downloadfile as a means to download files from the
webserver to the local machine. However access to all paths isn't valid
(for obvious security reasons). Is there a work around for this, or a means
that the end user can setup the destination directory without having to
worry about access violations?

Thanks in advance!




Access to the path "c:\dohaa.htm" is denied.


Exception Details: System.UnauthorizedAccessException: Access to the path
"c:\dohaa.htm" is denied.

ASP.NET is not authorized to access the requested resource. Consider
granting access rights to the resource to the ASP.NET request identity.
ASP.NET has a base process identity (typically {MACHINE}\ASPNET on IIS 5 or
Network Service on IIS 6) that is used if the application is not
impersonating. If the application is impersonating via <identity
impersonate="true"/>, the identity will be the anonymous user (typically
IUSR_MACHINENAME) or the authenticated request user.

To grant ASP.NET write access to a file, right-click the file in Explorer,
choose "Properties" and select the Security tab. Click "Add" to add the
appropriate user or group. Highlight the ASP.NET account, and check the
boxes for the desired access.

[Joerg Jooss]

jared wrote:

> I've been toying with an asp.net diretory browser and have been
> trying to use system.net.webclient.downloadfile as a means to
> download files from the webserver to the local machine. However
> access to all paths isn't valid (for obvious security reasons). Is
> there a work around for this, or a means that the end user can setup
> the destination directory without having to worry about access
> violations?

You always have to "worry" about security ;-)

There are basically two choices: Make as many directories as required
accessible to the ASPNET user (ouch!) or use impersonation so that ASP.NET
uses the identity provided by the client. I guess the latter makes more
sense for a web-based file browser, since all appropriate access rights
should already be in place.

Cheers,

--
Joerg Jooss
[url]www.joergjooss.de[/url]
[email]news@joergjooss.de[/email]