表单身份验证无限循环
我有一个在具有表单身份验证的本地主机上运行良好的应用程序。
我将其部署到部署机器上，并将其部署到构建机器上，并收到了无数的 302 重定向。
我尝试登录部署机器并通过部署机器 IP 访问该页面，它再次工作。
因此，当我尝试从我的计算机访问该站点到构建计算机时，它不起作用。
可能是什么原因造成的？
I have an application that works great on localhost with forms authentication.
I deployed it to the deployment machine and it to the build machine and received and endless set of 302 redirects.
I try logging onto the deployment machine and access the page via the deployment machines ip and it works again.
So it is not working when I try and access the site from my computer to the build computer.
What could be causing this?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
几周前我遇到了这个问题。我的问题是我的
Default.aspx需要我尝试登录的用户所没有的角色/权限。我通过删除默认页面所需的任何权限并确保 web.config 中的权限正常来修复此问题。
I had this problem a few weeks ago. My problem was that my
Default.aspxrequired roles/permissions that the user I was trying to log with did not have.I fixed it by removing any permissions required for my default page and making sure the permissions in my web.config were Ok.
很可能是 IIS 配置问题。
There's most likely an IIS configuration issue.
这是因为服务器上的时间与我的客户端计算机上的时间不同。谁知道会发生这样的事情？不是我。
可悲的是我在几个小时前更改了时间，但我把它设置为上午而不是下午。惊人的！
And it was because the time on the server was different then the time on my client machine. Who knew such a thing could happen? Not me.
The sad part is I changed the time hours ago but I put it at AM instead of PM. Awesome!
我通过将 ASP.NET 版本正确更改为 1.1.4322 而不是 2.0.50727（它的设置值），在装有 IIS 5.1 的 .NET 1.1 站点的 Windows XP 计算机上解决了此问题。
只是想提一下，以防它对其他人有帮助。我为没有早点意识到这一点而感到愚蠢。 :-)
I resolved this issue on a Windows XP machine with IIS 5.1 for a .NET 1.1 site by changing the ASP.NET version correctly to 1.1.4322 instead of 2.0.50727 (what it was set to).
Just wanted to mention that in case it helps someone else. I feel silly for not realising that sooner. :-)