Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.
Changed by [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=76735 --- shadow/76735 2005-11-17 14:03:00.000000000 -0500 +++ shadow/76735.tmp.32209 2005-11-17 14:03:00.000000000 -0500 @@ -0,0 +1,115 @@ +Bug#: 76735 +Product: Mono: Class Libraries +Version: unspecified +OS: All +OS Details: +Status: NEW +Resolution: +Severity: +Priority: Wishlist +Component: Sys.Web +AssignedTo: [EMAIL PROTECTED] +ReportedBy: [EMAIL PROTECTED] +QAContact: [EMAIL PROTECTED] +TargetMilestone: --- +URL: +Cc: +Summary: xmlns in asp.net web.config not accepted by xsp2 + +Description of Problem: +Default Vs.net2005 web.config fails on xmlns in the <configuration> tag + + +Steps to reproduce the problem: +1. Run xsp2 on a directory with below web.config +2. go there with the browser +3. + +Actual Results: +error: +----------------------------------------------- +System.TypeInitializationException: An exception was thrown by the type +initializer for Mono.WebServer.XSPWorkerRequest + +Server stack trace: +in <0x00000> <unknown method> +in <0x00150> Mono.WebServer.XSPApplicationHost:ProcessRequest (Int32 reqId, +Int64 localEPAddr, Int32 localEPPort, Int64 remoteEPAdds, Int32 +remoteEPPort, System.String verb, System.String path, System.String +queryString, System.String protocol, System.Byte[] inputBuffer, +System.String redirect, IntPtr socket, Mono.WebServer.SslInformations ssl) +in (wrapper remoting-invoke-with-check) +Mono.WebServer.XSPApplicationHost:ProcessRequest +(int,long,int,long,int,string,string,string,string,byte[],string,intptr,Mono.WebServer.SslInformations) +in (wrapper xdomain-dispatch) +Mono.WebServer.XSPApplicationHost:ProcessRequest +(object,byte[]&,byte[]&,int,long,int,long,int,string,string,string,string,byte[],string) + +Exception rethrown at [0]: + ---> System.Configuration.ConfigurationException: Unrecognized attribute +in root element (c:/inetpub/wwwroot/library\Web.config line 10) +in <0x00043> System.Configuration.ConfigurationData:ThrowException +(System.String text, System.Xml.XmlTextReader reader) +in <0x00082> System.Configuration.ConfigurationData:InitRead +(System.Xml.XmlTextReader reader) +in <0x00098> System.Configuration.ConfigurationData:Load (System.String +fileName)--- End of inner exception stack trace --- + +in (wrapper xdomain-invoke) +Mono.WebServer.XSPApplicationHost:ProcessRequest +(int,long,int,long,int,string,string,string,string,byte[],string,intptr,Mono.WebServer.SslInformations) +in (wrapper remoting-invoke-with-check) +Mono.WebServer.XSPApplicationHost:ProcessRequest +(int,long,int,long,int,string,string,string,string,byte[],string,intptr,Mono.WebServer.SslInformations) +in <0x00563> Mono.WebServer.XSPWorker:InnerRun (System.Object state) +in <0x00022> Mono.WebServer.XSPWorker:Run (System.Object state) +----------------------------------------------- +Expected Results: +asp.net page in that dir + +How often does this happen? +Always + +Additional Information: +<?xml version="1.0"?> +<!-- + Note: As an alternative to hand editing this file you can use the + web admin tool to configure settings for your application. Use + the Website->Asp.Net Configuration option in Visual Studio. + A full list of settings and comments can be found in + machine.config.comments usually located in + \Windows\Microsoft.Net\Framework\v2.x\Config +--> +<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0"> + <appSettings/> + <connectionStrings/> + <system.web> + <!-- + Set compilation debug="true" to insert debugging + symbols into the compiled page. Because this + affects performance, set this value to true only + during development. + --> + <compilation debug="true"> + <assemblies> +</assemblies></compilation> + <!-- + The <authentication> section enables configuration + of the security authentication mode used by + ASP.NET to identify an incoming user. + --> + <authentication mode="Windows"/> + <!-- + The <customErrors> section enables configuration + of what to do if/when an unhandled error occurs + during the execution of a request. Specifically, + it enables developers to configure html error pages + to be displayed in place of a error stack trace. + + <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm"> + <error statusCode="403" redirect="NoAccess.htm"/> + <error statusCode="404" redirect="FileNotFound.htm"/> + </customErrors> + --> + </system.web> +</configuration> _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
