New Bug, bugger it all! I am logged in but can't vote.
That's it. Had trouble posting a comment and then it duplicated itself.
I've logged out and back in with success but am still getting the "Hey, you have to buy woot stuff" notice.
Edit: 30 seconds after posting this question, it seems to have been resolved but I'm leaving this up just in case. Staff can delete if need be.
by
lavikinga
asked 2 years ago
This is ALWAYS a synchronization problem with account.woot.com and deals.woot.com (deals has to know you bought something to let you vote, and if it can't ask account whether you did, it's not going to let you play).
This was how all this scary mess started from yesterday, so I'm just giving a slight heads up to the terrible duo, @shawnmiller and @josefresno.
No reply necessary, but just in case things are starting to be wonky again, I'm poking you.
that happened to me yesterday I just refreshed the page and all was well.
@hobbit: That's what I thought should've taken care of that little gremlin as well, but even logging out, quitting my browser and logging back in gave me the same results. I didn't clear my cache and I of course allow deals to bake cookies in my browser's oven as well. It was just weird how one minute I was fine and the next thing, there was that sinking feeling and a band playing in the background.
This happens to me all the time, except some times I can't even get back in for a bit.
Normally what fixes mine is closing the browser and reopening.
@shawnmiller and @josefresno: I believe that there are ever increasing errors on the account.woot.com side, rather than on deals. I've watched the authentication just vanish from one click to the next, and I'm really apologetic that I don't currently have a test suite of machines to check on this. I don't believe that the account.woot.com world is your responsibility, but you might consider passing this along to whoever owns that process/server.
On the other hand, maybe you do have ownership of it, in which case I've already reached the source. I'm not seeing any one thing lead up to the loss of authentication, but I will try to start paying attention to what precise actions I'm taking that seem to lead up to it.
@shrdlu: Thanks for the heads up.
We did a funny thing and made sure we patched all our web servers to fix an ASP.NET vulnerability. This caused some unexpected and wicked problems as the patch made its way across all machines in the cloud and in the data center.
This left a portion of our members in log in hell, just prompting them to log in over and over again. I'm pleased to report we're in good shape now, and the error log is slowing to a crawl.
If you really want to geek out you can read the section about Persistent Forms Authentication Cookie Behavior here: http://weblogs.asp.net/scottgu/archive/2010/09/30/asp-net-security-fix-now-on-windows-update.aspx
For those who were interested, or curious, here's the write up on the specific bug that Shawn was referring to.
http://blog.mindedsecurity.com/2010/10/breaking-net-encryption-with-or-without.html
Ah, Microsoft, the infosec world has such a love/hate relationship with you. Yes, you provide full employment, but your bugs are so predictable.
7 Answers answer
Sort By: