Re: Passing custom headers to login page

The viewstate should only matter if you're using the same form names as
your server controls are expecting. If you rid yourself of either server
controls or use different form names, then viewstate shouldn't be an
issue.

If the servers are in the same domain, a cookie would be the way to pass
custom headers along. You could also use XmlHttpRequest to do the login,
and then Javascript load the resulting page. I'm not up on the current
XHR limitations, but my recollection is at least 1 major browser doesn't
allow cross domain requests - so you'd have to have your servers in the
same domain (at which point, I'd just use a cookie).

--MB

-----Original Message-----
From: Discussion of advanced .NET topics.
[mailto:[email protected]] On Behalf Of Mont
Rothstein
Sent: Friday, October 10, 2008 1:02 PM
To: [email protected]
Subject: Re: [ADVANCED-DOTNET] Passing custom headers to login page

Adam, thanks, you have been a huge help.
The FormsAuthentication methods were what I was missing.

Re-writing the response to be an auto-submitting page didn't work
because
ASP.NET was po'd that the view state wasn't there.

My custom header idea seems to be a no-go because there is no way to add
custom headers to a re-directed response.

That seems to leave me with having to pass the username and password in
the
query string.

Do you see any other option (other than not doing this cross-site
autologin
at all :-) ?

Thanks again,
-Mont

===================================
View archives and manage your subscription(s) at
http://peach.ease.lsoft.com/archives

===================================
View archives and manage your subscription(s) at http://peach.ease.lsoft.com/archives