My partner was successful with Lambda, and landed a good job with a Fortune 500 company. We don't consider Lambda a scam at all. It's not the same thing as college. Lambda's shortcomings are well publicized, and he went into it expecting to deal with those challenges. But it's not worthless either. He went into it expecting something like guided self-study on steroids, and he got better than that, with invaluable coaching and job placement services. His ISA is over $700/mo, but he's already come out ahead of his old minimum wage salary even accounting for the year off work to study.

Lambda has a lot of work to really be the future of education, but for our sample size of one, it's a great success.

This patch broke the auth for some of my web-based software packages :-(

We had the need to use .htaccess auth instead of cookie auth, but since the software is heavily used on public terminals we also have the need for a functional [LOGOUT] button.

My logout button would direct the user to a seperatly .htaccess protected folder, with the same ID as the actual software, but with a new username of 'please_enter_your_email'

This caused IE to 'forget' it's previous auth information and store the new one.

Then, if somebody tried to use the back button on a public terminal to re-enter the software, they would get the auth box. (unlike with cookies, where the cached page may still appear, because ie6 likes to ignore no-cache directives)

But now, as users patch their systems, my logout button will be broken and give an 'invalid syntax' error.

Is there some other way to force the IE browser to forget browser auth information?