HttpWebResponse.GetResponse() fiddler 说“响应标头解析失败。 ”

发布于 2024-12-25 12:01:03 字数 1415 浏览 1 评论 0原文

我正在通过 HttpWebRequest/HttpWebResponse 对象向网站发出请求。

我对网站进行了几次成功的调用，但对同一动态页面的所有其他调用都失败了。

在调试器中，我收到“内部服务器错误 500”fiddler 还显示 500 响应并包含：

[Fiddler] Response Header parsing failed.
This can be caused by an illegal HTTP response earlier on this reused server socket--     for instance, a HTTP/304 response which illegally contains a body.
Response Data:
<plaintext> 
0D 0A 3C 21 44 4F 43 54 59 50 45 20 48 54 4D 4C 20 50 55 42 4C 49 43 20  ..<!DOCTYPE      HTML PUBLIC 
22 2D 2F 2F 57 33 43 2F 2F 44 54 44 20 48 54 4D 4C 20 34 2E 30 20 54 72  "-//W3C//DTD HTML 4.0 Tr
61 6E 73 69 74 69 6F 6E 61 6C 2F 2F 45 4E 22 3E 0D 0A 3C 48 54 4D 4C 3E  ansitional//EN">..<HTML>
0D 0A 09 3C 48 45 41 44 3E 0D 0A 09 09 3C 74 69 74 6C 65 3E 56 69 65 77  ...<HEAD>....<title>View

我已删除所有十六进制并查看了页面，这是我期望返回的内容，但由于某种原因服务器正在报告500 并且 HttpWebRequest 对象对此抛出异常。

我已经尝试了此问题的所有其他“修复”，但没有任何效果。它可能只是从服务器发送的格式错误的数据，但是是否有比 HttpWebRequest 更低级别的对象可供使用，而不是皮塔饼？

编辑：在上面的示例中我没有包含整个十六进制/整个 html 块。
编辑：关闭fiddler我在调试器中得到了这个

编辑：因此，从我所看到的HttpWebResponse对象正在相应地起作用。服务器只是不稳定，有时会返回具有不同 http 状态代码的相同数据。为了快速修复，我只是将每个调用包装在 try/catch 中，并在 catch 块中重新执行完全相同的调用。到目前为止，它工作得很好，并且半证明了这是站点的错误，而不是 HttpWebResponse 对象的错误。

The server committed a protocol violation. Section=ResponseStatusLine

原文

I'm making a request to a website via the HttpWebRequest/HttpWebResponse objects.

I'm making several successful calls to the web site and every other call to the same dynamic page is failing.

In the debugger I'm getting a "Internal server error 500" fiddler also shows a 500 response and contains:

[Fiddler] Response Header parsing failed.
This can be caused by an illegal HTTP response earlier on this reused server socket--     for instance, a HTTP/304 response which illegally contains a body.
Response Data:
<plaintext> 
0D 0A 3C 21 44 4F 43 54 59 50 45 20 48 54 4D 4C 20 50 55 42 4C 49 43 20  ..<!DOCTYPE      HTML PUBLIC 
22 2D 2F 2F 57 33 43 2F 2F 44 54 44 20 48 54 4D 4C 20 34 2E 30 20 54 72  "-//W3C//DTD HTML 4.0 Tr
61 6E 73 69 74 69 6F 6E 61 6C 2F 2F 45 4E 22 3E 0D 0A 3C 48 54 4D 4C 3E  ansitional//EN">..<HTML>
0D 0A 09 3C 48 45 41 44 3E 0D 0A 09 09 3C 74 69 74 6C 65 3E 56 69 65 77  ...<HEAD>....<title>View

I've removed all the hex and viewed the page and is what I expect to be returned but for some reason the server is reporting a 500 and the HttpWebRequest object throws an exception on this.

I've tried all the other "fixes" for this issue and none work. It might just be malformed data sent from the server but is there a lower level object to use than HttpWebRequest that's not a pita to work with?

EDIT: I didn't include the entire hex/entire html block in the above example.
EDIT: Turning off fiddler I get this in the debugger

EDIT: So, from what I've seen the HttpWebResponse object is acting accordingly. The server is just flaky and sometime returns the same exact data with different http status codes. For a quick fix I just wrapped each call in a try/catch and in the catch block just retying the exact same call. So far it works great and semi-proves that it's the sites fault and not the HttpWebResponse object.

The server committed a protocol violation. Section=ResponseStatusLine

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

酒废 2025-01-01 12:01:03

HTTP 304 响应意味着自上次访问页面以来页面内容没有更改（它们可能使用缓存）。减少访问页面的频率或缓存响应以供遇到这种情况时使用。

编辑

服务器正在发送包含数据的无效 304 响应。这违反了 HTTP 规范，并且 HttpWebResponse/Fiddler 正在有效地将其转换为 500。

编辑

如果您在 app.config 中使用以下设置，您也许可以继续使用 HttpWebRequest/HttpWebResponse：

<configuration>
    <system.net>
        <settings>
            <httpWebRequest useUnsafeHeaderParsing="true" />
        </settings>
    </system.net>
</configuration>

An HTTP 304 response means that the page content has not changed since the last time you hit the page (they're likely using caching). Hit the page less often or cache the response for use when this is encountered.

EDIT

The server is sending an invalid 304 response which contains data. This violates the HTTP spec and the HttpWebResponse/Fiddler is validly transforming it into a 500 as such.

EDIT

You may be able to keep using the HttpWebRequest/HttpWebResponse if you use the following setting in your app.config:

<configuration>
    <system.net>
        <settings>
            <httpWebRequest useUnsafeHeaderParsing="true" />
        </settings>
    </system.net>
</configuration>

回复收藏 0 原文