Visual Studio ASP.NET 开发服务器开始返回 HTTP 503 错误的原因是什么？
我已经花了几周时间搭建一个网站，大部分日常工作只是使用母版页创建新的 Web 表单。我一直在使用 ASP.NET 开发服务器来查看我对项目的添加，但今天（似乎突然出现）服务器返回了 HTTP 503 错误。我尝试重新启动 VS，然后重新启动工作站，然后确保在我的工作站上启用“绕过本地地址代理”，但无济于事。有人以前遇到过这种行为吗？或者有人对我可以查看以进行调查的日志有建议吗？提前致谢。
更新：使用 telnet 时，服务器返回看似 ASP.NET 服务器页面的标记，列出 HTTP 错误 400 - 错误请求。在 Google Chrome 中仍然出现 503，在 Firefox 和 Internet Explorer 中仍然出现空白页。
I've been putting together a website for a few weeks, most of the routine has just been creating new web forms with master pages. I've been using the ASP.NET Development Server to view my additions to the project as I've gone along, but today (seemingly out of nowhere) the server has been returning HTTP 503 errors. I tried restarting VS, then restarting workstation, then making sure that "bypass proxy for local addresses" was enabled on my workstation, but to no avail. Has anyone encountered this behavior before or does anyone have suggestions on logs I can review to investigate? Thanks in advance.
Update: When using telnet, the server returns the markup for what looks to be an ASP.NET server page, listing an HTTP Error 400 - Bad Request. Still getting a 503 in Google Chrome and blank pages in Firefox and Internet Explorer.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
1）可能web.config有错误，所以cassini无法理解。尝试发布网站并使用普通 IIS 运行它
2) 从项目根目录中删除文件 app_offline.htm。 cassini确实产生了503错误
1) Maybe there is errors in web.config, so cassini can't understand it. Try to publish website and run it with normal IIS
2) Remove file app_offline.htm from root of your project. It's really generate 503 error with cassini
您是否尝试过在 Web 应用程序中启用调试？
http://msdn.microsoft.com/en -us/library/e8z01xdh%28v=vs.80%29.aspx
did u tried enabling debugging in your web application?
http://msdn.microsoft.com/en-us/library/e8z01xdh%28v=vs.80%29.aspx
一种可能性是某些其他应用程序（例如在 IIS 中）现在配置为侦听同一端口/vdir 组合。这可能是两个站点/服务器/应用程序之间的端口冲突。我会使用 Fiddler 工具 来查看响应标头并查看是否从以下位置获得响应您期望的服务器。
One possibility is that some other application is now configured, say, in IIS, to listen on the same port/vdir combination. It might be a port conflict between two site/servers/applications. I would get Fiddler tool to look at response headers and see whether you are getting the response from the server you expect.