Rodney,
I'm not positive but it appears that this is not a Repository problem at all. It's possible that it's a DotNetNuke issue. There are a number of posts in other forums that are reporting issues of users getting logged out. We talked about it for some time last night in the core team chat and the theory is that the authorization cookie is being deleted by some dnn process. It sounds very similar to the cookie errors we're seeing in the Repository, where the authorizaton cookie just 'disappears' and then when I attempt to redirect back to the page you came from after downloading, dnn can't figure out who you are since the cookie is gone.

Exactly what version of DNN are you running? from your first post, it looks like 3.2.0 .. is that right?

---

Steve Fabian e: steve.fabian@gooddogs.com w: http://www.gooddogs.com

Steve, I've been running the latest production version on my servers and have the same compression settings on both installs. You might remember me mentioning in an email that I was the cookie problem on one install but not on the other which was really confusing. I'll check the schedules on the sites this evening if I get the chance (I'm on course this week and next and getting a ton of homework) and see if there are any differences that might point to what you've posted in the last couple of threads and in the link you posted.