[Mono-bugs] [Bug 650695] New: System.Web.HttpNotFoundHandler missing

[bugzilla_noreply at novell.com]

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

https://bugzilla.novell.com/show_bug.cgi?id=650695#c0


           Summary: System.Web.HttpNotFoundHandler missing
    Classification: Mono
           Product: Mono: Class Libraries
           Version: 2.6.x
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Sys.Web
        AssignedTo: mhabersack at novell.com
        ReportedBy: oskar.berggren at gmail.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---


User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.12)
Gecko/20101027 Ubuntu/10.04 (lucid) Firefox/3.6.12

The HttpNotFoundHandler class is missing from System.Web.

A believe this class is internal, and so not part of the API in the traditional
sense. It can, however, be referenced from web.config.

Specifically, the default project template for ASP.Net MVC uses the following
snippet in the web.config within the Views folder to prevent direct access to
the views:

  <httpHandlers>
      <add path="*" verb="*" type="System.Web.HttpNotFoundHandler"/>
  </httpHandlers>

When running such a solution on Mono, you get 500 Internal server error, with
the message "Failed to load httpHandler type `System.Web.HttpNotFoundHandler'".
Expected behavior is of course to instead get a 404 Not found message.

As a test case, I suggest creating an ASP.Net MVC project with Monodevelop, and
try to browse directly to a view file under the Views folder, to expose the
above error.

A patch has been provided here:
http://lists.ximian.com/pipermail/mono-devel-list/2009-June/032365.html

And then again here, with some discussion also:
http://lists.ximian.com/pipermail/mono-devel-list/2009-November/033388.html


Reproducible: Always

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