[Mono-bugs] [Bug 643255] New: Inconsistent behavior between mono and .net on authorization defined at Web.conf

[bugzilla_noreply at novell.com]

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

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


           Summary: Inconsistent behavior between mono and .net on
                    authorization defined at Web.conf
    Classification: Mono
           Product: Mono: Class Libraries
           Version: SVN
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Sys.Web
        AssignedTo: mhabersack at novell.com
        ReportedBy: pruiz at netway.org
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---


User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US)
AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.472.63 Safari/534.3

When using a 'location' node on Web.config to allow unrestricted access to a
directory, .Net allows access to such directory and any other directory below
it.

However, mono seems to only allow access to files within the directory itself
'only'.

Example: using the following config:

    <location path="Content">
        <system.web>
            <authorization>
                <allow users="*"/>
            </authorization>
        </system.web>
    </location>

On MS.Net, it will allow access to /Content/file.jpg as well as
/Content/Subdir/file.jpg.

However on mono accessing /Content/file.jpg works, but /Content/Subdir/file.jpg
fails due to authentication/authorization needed.


Reproducible: Always

Steps to Reproduce:
1. Create a sample web project.
2. Create a /Content/Subdir hierachy
3. Add a location directive to Web.config like the one shown at description.
4. Try to access a file under Subdir.
Actual Results:  
Access not allowed.

Expected Results:  
Access allowed.

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