mail-archives/mono-bugs/2004-June/018025.html

131 строка
5.4 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mono-bugs] [Bug 60739][Blo] New - ASP.NET Trace pageOutput and localOnly Bug(s)
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:bugzilla-daemon%40bugzilla.ximian.com">
<META NAME="robots" CONTENT="index,nofollow">
<LINK REL="Previous" HREF="018024.html">
<LINK REL="Next" HREF="018026.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mono-bugs] [Bug 60739][Blo] New - ASP.NET Trace pageOutput and localOnly Bug(s)
</H1>
<B>bugzilla-daemon@bugzilla.ximian.com
</B>
<A HREF="mailto:bugzilla-daemon%40bugzilla.ximian.com"
TITLE="[Mono-bugs] [Bug 60739][Blo] New - ASP.NET Trace pageOutput and localOnly Bug(s)">bugzilla-daemon@bugzilla.ximian.com
</A><BR>
<I>Fri, 25 Jun 2004 06:56:24 -0400 (EDT)</I>
<P><UL>
<LI> Previous message: <A HREF="018024.html">[Mono-bugs] [Bug 60442][Maj] Changed - PrivateBinPath bug again...
</A></li>
<LI> Next message: <A HREF="018026.html">[Mono-bugs] [Bug 60742][Nor] New - DataSet Xml Schema Inference bug on MONO
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#18025">[ date ]</a>
<a href="thread.html#18025">[ thread ]</a>
<a href="subject.html#18025">[ subject ]</a>
<a href="author.html#18025">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>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 <A HREF="mailto:davidandrewtaylor@hotmail.com.">davidandrewtaylor@hotmail.com.</A>
<A HREF="http://bugzilla.ximian.com/show_bug.cgi?id=60739">http://bugzilla.ximian.com/show_bug.cgi?id=60739</A>
--- shadow/60739 2004-06-25 06:56:24.000000000 -0400
+++ shadow/60739.tmp.7256 2004-06-25 06:56:24.000000000 -0400
@@ -0,0 +1,67 @@
+Bug#: 60739
+Product: Mono: Class Libraries
+Version: unspecified
+OS: Red Hat 9.0
+OS Details:
+Status: NEW
+Resolution:
+Severity:
+Priority: Blocker
+Component: Sys.Web
+AssignedTo: <A HREF="mailto:mono-bugs@ximian.com">mono-bugs@ximian.com</A>
+ReportedBy: <A HREF="mailto:davidandrewtaylor@hotmail.com">davidandrewtaylor@hotmail.com</A>
+QAContact: <A HREF="mailto:mono-bugs@ximian.com">mono-bugs@ximian.com</A>
+TargetMilestone: ---
+URL:
+Summary: ASP.NET Trace pageOutput and localOnly Bug(s)
+
+Description of Problem:
+There are 2 nasty bugs in MONO (I checked in the current CVS built)
+regarding the ASP.NET trace feature.
+
+Take this web.config setting:
+&lt;trace enabled=&quot;true&quot; pageOutput=&quot;false&quot; localOnly=&quot;true&quot; /&gt;
+SUMMARY:
+Bug A) Mono ignores the PageOutput setting and always outputs trace
+information to the page irrespective of this setting.
+Bug B) The localOnly setting is incorrectly implemented and decides if
+the request is local or remote only on the first request (when the page
+is parsed) and all future requests incorrectly use this same setting.
+DETAIL:
+Bug A: pageOutput
+The pageOutput attribute can be used to stop trace information appearing
+at the bottom of an ASPX web page (but you can still view it via the
+Trace.axd handler). I assume this can be easily fixed in &quot;Page.cs&quot; by
+changing the method &quot;private void RenderTrace (HtmlTextWriter output)&quot;.
+It could be as easy as changing the last line from:
+- Trace.Render (output);
+to
++ if (HttpRuntime.TraceManager.PageOutput) Trace.Render (output);
+
+I have not tried the above fix but it would appear correct?
+
+Bug B): localOnly
+If localOnly=&quot;true&quot; the Trace should only be shown when serving requests
+to a web browser on the same machine; however with the current
+implementation a boolean seems to be evaluated on the very first request
+(when the page is Parsed). So if the first request is from a localhost
+browser the page is correctly shown with trace information. If you then
+move to a remote browser and hit the page (without restarting XSP) the
+trace information will incorrectly be shown. And Visa-versa if you first
+view remotely the trace will correctly not be shown; but then if you view
+on localhost the trace will still not be shown (which is incorrect).
+
+In the class &quot;PageParser.cs&quot; there is a method &quot;internal override void
+ProcessMainAttributes (Hashtable atts)&quot;. Deep inside this method the
+following code appears:
+-----
+if (traceConfig.LocalOnly &amp;&amp; !Context.Request.IsLocal) {
+ haveTrace = false;
+ trace = false;
+}
+-----
+
+Obviously the decision as to if trace information is displayed needs to
+be made &quot;For Every Request&quot; and not just with the very first request.
+
+Let me know if I can help any further with this. Thanks.
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI> Previous message: <A HREF="018024.html">[Mono-bugs] [Bug 60442][Maj] Changed - PrivateBinPath bug again...
</A></li>
<LI> Next message: <A HREF="018026.html">[Mono-bugs] [Bug 60742][Nor] New - DataSet Xml Schema Inference bug on MONO
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#18025">[ date ]</a>
<a href="thread.html#18025">[ thread ]</a>
<a href="subject.html#18025">[ subject ]</a>
<a href="author.html#18025">[ author ]</a>
</LI>
</UL>
</body></html>