[Mono-bugs] [Bug 430488] New: HttpApplication.PipeLine assumes IAsyncResult. AsyncState is always IHttpAsyncHandler

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Sun Sep 28 11:05:24 EDT 2008


https://bugzilla.novell.com/show_bug.cgi?id=430488


           Summary: HttpApplication.PipeLine assumes IAsyncResult.AsyncState
                    is always IHttpAsyncHandler
           Product: Mono: Class Libraries
           Version: unspecified
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Sys.Web
        AssignedTo: mhabersack at novell.com
        ReportedBy: jhill at novell.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: Product Management


Created an attachment (id=242125)
 --> (https://bugzilla.novell.com/attachment.cgi?id=242125)
Simple IHttpAsyncHandler implementation

Description of Problem:
In a simple IHttpAsyncHandler implementation, executing the AsyncCallback
argument
of BeginProcessRequest with a default implementation of IAsyncResult will throw
a NullReferenceException.


Steps to reproduce the problem:
Save the attached simple IHttpAsyncHandler implementation as
SimpleHttpAsyncHandler.ashx.

In the same directory where SimpleHttpAsyncHandler.ashx is saved, execute:
xsp2 --port 8080

Browse to http://localhost:8080/SimpleHttpAsyncHandler.ashx

Actual Results:
Server Error in '/' Application
Object reference not set to an instance of an object

Description: HTTP 500. Error processing request.

Stack Trace:

System.NullReferenceException: Object reference not set to an instance of an
object
  at System.Web.HttpApplication.async_handler_complete_cb (IAsyncResult ar)
[0x00000] 

Version information: Mono Version: 2.0.50727.42; ASP.NET Version: 2.0.50727.42

Expected Results:
Success!

How often does this happen? 
Always

Additional Information:
None


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the mono-bugs mailing list