Schevenels
Fri Jun 22 04:58:26 CDT 2007
Thank you.
"David Wang" <w3.4you@gmail.com> a écrit dans le message de
news:1182504629.764601.165770@x35g2000prf.googlegroups.com...
On Jun 22, 1:49 am, "Schevenels Patrick" <psche...@hotmail.com> wrote:
> Hello.
>
> When I want to access an .aspx page on my IIS 7.0 server on Windows Vista,
> I
> get this error message (I don't get it when I use .htm pages) :
>
> Erreur HTTP 404.3 - Not Found
> Description : La page que vous avez demandée est introuvable en raison de
> la
> stratégie de mappage MIME (Multipurpose Internet Mail Extensions)
> configurée
> sur le serveur Web. La page que vous avez demandée possède une extension
> de
> nom de fichier non reconnue et non autorisée.
>
> Code d'erreur : 0x80070032
>
> Notification : ExecuteRequestHandler
>
> Module : StaticFileModule
>
> URL demandée :
http://localhost:80/test.aspx
>
> Chemin d'accès physique : E:\inetpub\wwwroot\test.aspx
>
> Session utilisateur : Anonyme
>
> Méthode d'ouverture de session : Anonyme
>
> Gestionnaire : StaticFile
>
> Thank you for your answers.
>
> Patrick Schevenels
The reason it does not work by default is because of security -- IIS7
does not support executing anything, including ASP.Net pages, by
default.
The error says that you are trying to download an ASPX file and the
StaticFile Handler does not permit that by default. However, that is
not the real problem.
ASPX file is supposed to be executed on the server to generate the
HTML page, so this error actually indicates that ASPX is not
configured to execute on the server.
Default IIS7 installation only serves static files and does not
execute code like ASP.Net.
Thus, the real problem is that you failed to install ASP.Net support
for IIS7, and IIS7 is behaving exactly as you told it to -- fail to
execute ASP.Net pages.
Please go to "Windows Features" and install ASP.Net support for IIS7.
It can be found in:
Control Panel>Programs>Programs and Features>Windows Features>Internet
Information Services>World Wide Web Services>Application Development
Features>ASP.Net
It will also check .NET Extensibility, ISAPI Extensions, and ISAPI
Filters. If you never plan to run ASP.Net in classic compatibility
mode, then you can uncheck the ISAPI Extension and ISAPI Filters
checkboxes because they will not be necessary.
Now, if you do not know what you need and do not want to deal with
things "not working", you *can* choose to check everything. However,
you bear full responsibility for security at that point. No, it's not
because Microsoft does not shoulder security responsibility - it
already does plenty; it is because users are equally responsible for
their computer's security, and this is but one lesson.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//