[Mono-bugs] [Bug 542846] New: System.Web.HttpResponse.Redirect doesn't use useFullyQualifiedRedirectUrl setting

[bugzilla_noreply at novell.com]

http://bugzilla.novell.com/show_bug.cgi?id=542846


           Summary: System.Web.HttpResponse.Redirect doesn't use
                    useFullyQualifiedRedirectUrl setting
    Classification: Mono
           Product: Mono: Class Libraries
           Version: 2.4.x
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Sys.Web
        AssignedTo: mhabersack at novell.com
        ReportedBy: brett at fogcreek.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---


Created an attachment (id=320268)
 --> (http://bugzilla.novell.com/attachment.cgi?id=320268)
A (probably wrong in many cases) patch that fixes this for our use cases

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1.3)
Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729)

When I set useFullyQualifiedRedirectUrl="True" I still don't get fully
qualified URLS in my 302s.

Here's a simple patch that gets this working for our use cases, but I'm not
really up on the subtleties, here, so use with caution.

Reproducible: Always

Steps to Reproduce:
In an XSP app:
1. Add <httpRuntime executionTimeout="300" maxRequestLength="1048576" 
useFullyQualifiedRedirectUrl="True" /> to your web.config.
2. Set up Fiddler or some such to show you what's really happening with your
HTTP responses.
2. Hit a page on your site that does a response.Redirect("blah.aspx")
3. Look at the 302 response.
Actual Results:  
Redirected to relative url /blah.aspx

Expected Results:  
Redirected to the absolute URL http://theserver/blah.aspx

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