哪些特定状态代码会导致 HttpWebRequest.GetResponse() 抛出 WebException？
我一直在寻找一些关于这方面的明确文档，但没有找到任何相关的运气。
对于哪些 HTTP 响应状态代码，在执行 POST 之类的操作后，HttpWebRequest.GetResponse() 会生成 WebException？
具体来说，除了状态 200 OK 之外，它是否会生成 WebException ？或者它只会为 400、404 和 500 生成 WebException（为了论证）？
我想知道，因为我正在通信的服务器定义了除 HTTP 200 OK 以外的任何内容作为错误条件返回。我可以依赖为除 200 之外的任何内容生成的 WebException 吗？
我目前已编写代码来每次检查返回状态代码并确保其为 200 OK。如果不是，它将采取适当的操作，但该代码和我希望清理的 WebException 的 catch 块之间存在大量重复。
任何相关的文档链接将不胜感激。
I've hunted around for some definitive documentation on this but haven't had much luck finding any.
For which HTTP Response Status codes will HttpWebRequest.GetResponse() generate a WebException after doing something like a POST?
Specifically, will it generate a WebException for anything other than status 200 OK? Or will it only generate a WebException for say, 400, 404, and 500 (for the sake of argument)?
I want to know since the server I'm communicating with defines anything other than HTTP 200 OK coming back as an error condition. Can I rely on a WebException being generated for anything other than 200?
I've currently written my code to check the return status code every time and ensure it's 200 OK. If it's not, it will take appropriate action—but there's a lot of duplication between that code and the catch block for a WebException that I'm hoping to clean up.
Any relevant links to documentation would be most appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
最终在响应后进行了明确的检查&捕获并检查 WebException；导致一些重复的代码，但对于如果状态不是 200 是否总是会发生 WebException 没有明确的答案。
Ended up doing an explicit check after the response & catching and checking WebExceptions; results in some duplicated code but there's no definitive answer on whether a WebException will ALWAYS occur if the status is NOT 200.
我认为会的，但这听起来像是一个冒险的假设。一方面，MSDN 文档很明显，
GetResponse会抛出WebException以外的异常。但是，根据经验，我可以肯定地说“304 Not-Modified”响应将作为WebException抛出。所有这些谈话都散发着一股难闻的代码气味；不要使用异常来控制执行流程。您最好适当地处理异常，然后显式检查
StatusCode属性以获得允许的值。I think it will, but it sounds like a risky assumption to make. For one thing, the MSDN docs make it clear that
GetResponsewill throw exceptions other than justWebException. However, I can say for definite from experience that a "304 Not-Modified" response will be thrown as aWebException.All this talk is giving off a whiffy Code Smell; don't use exceptions to control the flow of execution. You would be better off handling exceptions appropriately, then explicitly checking the
StatusCodeproperty for your allowable values.WebException 系统是独立的系统，与HTTP 错误系统。
这主要是因为 HTTP 错误是由浏览器或客户端返回的，而 WebException 是在构建页面时由服务器抛出的。当发现 HTTP 错误时，页面将发送到客户端，而您不会知道这一点。
The WebException system is seperate system from the HTTP error system.
This is mainly because the HTTP errors are returned by the browser or client and the WebException is thrown by the server while building your page. By the time an HTTP error is found the page is sent to the client and you won't know about it.