[Mono-bugs] [Bug 78219][Wis] New - Login control bug with master pages

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by grendello at gmail.com.

http://bugzilla.ximian.com/show_bug.cgi?id=78219

--- shadow/78219	2006-04-27 05:51:18.000000000 -0400
+++ shadow/78219.tmp.9519	2006-04-27 05:51:18.000000000 -0400
@@ -0,0 +1,41 @@
+Bug#: 78219
+Product: Mono: Class Libraries
+Version: 1.1
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Wishlist
+Component: Sys.Web
+AssignedTo: toshok at ximian.com                            
+ReportedBy: grendello at gmail.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Login control bug with master pages
+
+The attached patch fixes two problems with the Login control in Mono:
+
+ - As per
+http://msdn2.microsoft.com/en-us/library/system.web.ui.webcontrols.login.destinationpageurl.aspx
+   the patch makes Login redirect the user to destination page, in the
+   following precedence:
+                        
+     - DestinationPageUrl property
+     - Referring page             
+     - Forms authentication defaultUrl
+     - The login page itself          
+
+ - When the login control is used inside a content placeholder with a master
+   page (e.g.
+http://asp.net/QuickStart/util/srcview.aspx?path=~/aspnet/samples/ctrlref/login/Login.src)
+   Mono will throw an exception referring to line 1332 in Login.cs. The
+   patch fixes that by checking whether FormsAuthentication.LoginUrl is not
+   null.
+   I'm not sure whether the fix is correct, though, since the bug might be
+   in FormsAuthentication code. The reason might be that the Initialize
+   method of the FormsAuthentication class is not called before
+   Login.IsDefaultLoginPage(). The attached files provide the minimal test
+ case for the bug.