[Mono-bugs] [Bug 60180][Blo] New - Beta 3 bug: Default Trace settings in Web.config not being used.

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Tue, 15 Jun 2004 00:31:55 -0400 (EDT) 

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 davidandrewtaylor@hotmail.com.

http://bugzilla.ximian.com/show_bug.cgi?id=60180

--- shadow/60180	2004-06-15 00:31:54.000000000 -0400
+++ shadow/60180.tmp.18643	2004-06-15 00:31:54.000000000 -0400
@@ -0,0 +1,47 @@
+Bug#: 60180
+Product: Mono: Class Libraries
+Version: unspecified
+OS: Red Hat 9.0
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 001 One hour
+Priority: Blocker
+Component: Sys.Web
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: davidandrewtaylor@hotmail.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Beta 3 bug: Default Trace settings in Web.config not being used.
+
+Description of Problem:
+With Gonzalo's patch to 58481 I think we might have introduced or not 
+fixed another bug.  Now with Beta 3 trace settings in web.config for 
+enabled/disabled are not being used.  Also the localOnly setting appears 
+to not make any difference as either way trace results are appearing on 
+remote hosts (which is a security risk).
+
+Steps to reproduce the problem:
+web.config:
+<configuration>
+  <system.web>
+    <trace enabled="true" pageOutput="true" localOnly="true" />
+  </system.web>
+</configuration>
+
+<%@Page %>
+<html><body>Hello</body></html>
+
+Actual Results:
+Trace output does not appear.
+
+Expected Results:
+Trace output should appear because it is enabled in web.config.
+
+How often does this happen? 
+All the time.
+
+Additional Information:
+Bug 58481 was probably not fixed correctly.