[Mono-bugs] [Bug 686406] New: Accessing ASHX Causes Server to Throws Errors from Then On
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Fri Apr 8 18:23:37 EDT 2011
https://bugzilla.novell.com/show_bug.cgi?id=686406
https://bugzilla.novell.com/show_bug.cgi?id=686406#c0
Summary: Accessing ASHX Causes Server to Throws Errors from
Then On
Classification: Mono
Product: Mono: Runtime
Version: 2.10.x
Platform: x86-64
OS/Version: Other
Status: NEW
Severity: Critical
Priority: P5 - None
Component: misc
AssignedTo: mono-bugs at lists.ximian.com
ReportedBy: wswartzendruber at gmail.com
QAContact: mono-bugs at lists.ximian.com
Found By: ---
Blocker: ---
Created an attachment (id=424105)
--> (http://bugzilla.novell.com/attachment.cgi?id=424105)
The ASHX file that killed Kenny.
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.24 (KHTML,
like Gecko) Chrome/11.0.696.25 Safari/534.24
Mono ASP.NET continues to throw errors regarding "No Class attribute found."
once an ASHX has been accessed (which also raises this error). Restarting the
server (both Apache and mod-mono-server) have no effect.
Autoconfiguration is being used.
Reproducible: Always
Steps to Reproduce:
1. Create an ASPX page.
2. Request it from a client through Apache.
3. Observes that it works as intended.
4. Create a "Hello world." ASHX file.
5. Request it from a client through Apache.
6. Observe previously-mentioned exception.
7. Access the previously-mentioned ASPX page.
8. Observe the same behavior.
Actual Results:
The ASHX file throws the error and from then on out, so does the ASPX page.
Expected Results:
The ASHX file shouldn't throw this error. Also, the ASPX page should continue
to render, especially after the service has been restarted.
I'm running Gentoo Linux Hardened on an x86-64 VPS from HostVirtual.com.
"Hardened" means that PaX and GRSecurity are in effect. It is running a .38
kernel. GCC 4.5.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the mono-bugs
mailing list