.jpg)
Posts
All Comments
Don't worry I am still here - I just haven't posted for a while. A busy work load, focussed on Security (big post to come soon) and a large SQL based project (again post to come soon), a holiday and other things... Those are the excuses, I will post something technical soon, either about Android application development or RSS consumption with .NET.
A little treat for all you developers who have a sense of humor and are not offended by a little bad language.
To access a Session Variable from the front of your aspx page:
<script type="text/javascript" language="javascript" >
var varValue = '<%= Session["Key"] %>';
alert(varValue);
</script>
Not rocket science, but handy to know
I was having a play with Microsofts (relatively) new technology Photosynth over the Easter weekend, came up with this after a while.
It took a number of attemps to get it lookin this good and over 200 photos in total, that was cut down to 128 to make sure there was only "one image" displayed.
There is some nice detail near the base and the head, have a look around there are a few other areas of detail to explore.
I have been developing the login for a secure asp.net web application.
The application requires Forms Authentication with a pass through to a Windows Identity (see How To: Use Protocol Transition and Constrained Delegation in ASP.NET 2.0). To simplify matters I have been building up the security process in an empty web project.
having created a Forms Authentication web site (How To: Use Forms Authentication with Active Directory in ASP.NET 2.0) and implemented the Use Protocol Transition and Constrained Delegation (see link above) the login worked on the Visual Studio 2008 ASP.NET Development Server.
Next step was to release to a development server, the same Windows 2008 machine used to host the main application, following deployment the login failed.
Having searched a little I broke out Fiddler and discovered the Authentication Ticket/Cookie was set on login and then lost on redirect to the target secure page.
After a good nights sleep and fiddling around a little I verified the whole login process worked by placing the ticket on the URI, this however was not an acceptable solution.
Back to searching, this time I included IIS7 in my search and came up with this - I couldn't quite believe this was true, but it fixed my problem.
The test site I had created included an underscore in the URL, this was causing the cookie loss.
I have run this past a few colleagues and despite the use of an underscore in a URL not been common they knew of no real reason not to use one.
I hope this help someone out there.
