[Mono-bugs] [Bug 60739][Blo] Changed - ASP.NET Trace pageOutput and localOnly Bug(s)

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Tue, 29 Jun 2004 02:29:40 -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=60739

--- shadow/60739	2004-06-28 11:16:44.000000000 -0400
+++ shadow/60739.tmp.28940	2004-06-29 02:29:40.000000000 -0400
@@ -70,6 +70,78 @@
 Created an attachment (id=8376)
 Fixes this bug and also 60726
 
 
 ------- Additional Comments From gonzalo@ximian.com  2004-06-28 11:16 -------
 David, can you test that the patch works for you too? 
+
+------- Additional Comments From davidandrewtaylor@hotmail.com  2004-06-29 02:29 -------
+Gonzalo,
+
+We have been *way* wrong about how MS.NET handles ASP.NET Tracing.  
+I did a full test run today with 14 different scenarios on MONO and 
+MS.NET and realized our rules are incorrect.  I have tried to 
+summarize the rules we need to follow:
+
+* The ASPX Page Attribute Trace="true" enables both Tracing AND 
+PageOutput for a page IRRESPECTIVE of web.config settings.  Thus the 
+settings in web.config are irrelevent; if the page has a 
+Trace="true" attribute, trace output will be displayed at the bottom 
+of the page.
+
+* The ASPX Page Attribute Trace="false" disables both Tracing and 
+PageOutput for that page IRRESPECTIVE of web.config settings.  In 
+fact, TraceData is not even logged for the page, so if you view 
+Trace.axd nothing will have been logged if the page has a 
+Trace="false" attribute, even though tracing may have been enabled 
+in web.config.
+
+* In the absence of a Trace tag in the Page, the web.config settings 
+are used, and Trace output is only displayed at the bottom of a page 
+if pageOutput="true" has been set in web.config.
+
+Note: In the absense of trace settings in web.config the standard 
+values that appear in MS.NET machine.config are used which are:
+<trace enabled="false" localOnly="true" pageOutput="false" 
+requestLimit="10" traceMode="SortByTime"/>
+** Thus by defaut trace is disabled; pageOutput is disabled and 
+localOnly is set to true.
+
+Here are a number of failing tests after I applied your patch to RC1:
+
+web.config: <trace enabled="false" pageOutput="false" 
+localOnly="false" />
+<%@Page Trace="true" %>
+Trace Output Viewable : MS.NET=YES, MONO=NO   (Error)
+Trace.axd Is Viewable : MS.NET=NO , MONO=YES  (Error)
+
+web.config: <trace enabled="true" pageOutput="false" 
+localOnly="false" />
+<%@Page Trace="true" %>
+Trace Output Viewable : MS.NET=YES, MONO=NO   (Error)
+Trace.axd Is Viewable : MS.NET=YES ,MONO=YES (Correct)
+
+web.config: <trace enabled="true" pageOutput="true" 
+localOnly="false" />
+<%@Page Trace="false" %>
+Trace Output Viewable : MS.NET=NO, MONO=YES   (Error)
+Trace.axd Is Viewable : MS.NET=YES,MONO=YES (Correct)
+
+web.config: <configuration><system.web></system.web></configuration>
+Note: Thus no trace element in web.config
+<%@Page Trace="true" %>
+Trace Output Viewable : MS.NET=YES, MONO=NO   (Error)
+Trace.axd Is Viewable : MS.NET=YES ,MONO=YES (Correct)
+
+web.config: <trace enabled="true"/>
+<%@Page Trace="true" %>
+Trace Output Viewable : MS.NET=YES, MONO=NO   (Error)
+Trace.axd Is Viewable : MS.NET=YES ,MONO=YES (Correct)
+
+web.config: <trace enabled="false" />
+<%@Page Trace="true" %>
+Trace Output Viewable : MS.NET=YES, MONO=NO   (Error)
+Trace.axd Is Viewable : MS.NET=NO , MONO=YES  (Error)
+
+web.config: <trace pageOutput="true" />
+Trace.axd Is Viewable : MS.NET=NO, MONO=YES   (Error)
+