On Oct 15, 6:58 am, gazate <gaz... DeleteThis @h16-12networkx.de> wrote:
> Hi There,
>
> I´m trying to download a .resx file from an W2k3 SP2 IIS 6. The
> Problem:
>
> I can see the resx files when I browse the directory, but downloading
> or seeing them "as page" doesn´t work. I already deleted the .resx
> string from the configuration of the directory.
> Before it was deleted was the error (in the logs of the IIS) No. 403
> and 200. After deleting it is 404.
> So, the file is there and can not be run (403/200), but whe I try
> deleting .resx from the config the file is gone (the IIS thinks...).
> But I can see the file by listing the directory in IE an Firefox, but
> when I click the file: 404...
>
> Does someone know how to fix that problem?
>
> Thank you for your help!
>
> Gazate
The server is configured to actively prevent you from
downloading .resx files, so it's not exactly a "problem".
You can either:
1. change .config file to map .resx to the same handler as .aspx
Or you can:
1. Add MIME Type for .resx for that URL
2. Remove .resx Application Mapping for that URL
Basically, with all three of the above configurations, .resx is routed
from IIS to ASP.Net to its "forbidden" handler, which returns a 403,
and prevents download. To enable downloading, you have to break the
routing, which means you either change .config to route the .resx
request to a .Net static file handler that serves the file and won't
return 403, or you change .resx to be directly handled by the IIS
Static File Handler and not route it to ASP.Net and its "forbidden"
handler configuration.
Generally, changing the above configuration is incorrrect. What are
you really trying to accomplish?
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
FAQ
Profile
Private Messages
Log in
