firefox向后兼容性bug [英] firefox backwards compatability bug

查看:78
本文介绍了firefox向后兼容性bug的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在与旧服务器通信时遇到firefox坦克问题。


根据 http://www.w3.org/Protocols/HTTP/OldServers.html

如果没有响应行,流上的所有字节都将被视为text / html。


好​​吧我的firefox似乎部分锁定了这些响应。网页显示的部分是透明的,我看到的只是我的桌面(或其背后的任何内容)。


有谁知道我的补丁或某种插件可以修复这个错误吗?

I am having trouble with firefox tanking when talking to older servers.

As per http://www.w3.org/Protocols/HTTP/OldServers.html
If there is no response line, all bytes on the stream are to be treated as text/html.

Well my firefox appears to partially lock up on those responses. The section where the webpage would be displayed goes transparent and all I see is my desktop(or whatever is behind it).

Does anyone know of a patch or some sort of plugin that I can get to fix this bug?

推荐答案

需要一个例子,因为我从未听说过这个。
Need an example cause I''ve never heard of this.


似乎以某种方式与回复的大小相关。


" file is to large"是为特定请求返回的所有内容。没有任何状态代码或标题。它只返回那个短字符串然后关闭连接。


IE6显示它很好,这很有趣因为我知道IE(或者它是IIS5?)有某些响应的问题也是很小。


Firefox 2.0.0.6似乎可以解决这个问题。也许它只是在等待换行符或其他东西?但套接字连接已关闭,所以我认为它会停止,我不知道。
It seems to be related to the size of the response somehow.

"file is to large" is all that is returned for a certain request. No status code nor headers of any sort. It just returns that short string then closes the connection.

IE6 shows it just fine, which is funny because I know IE (or was it IIS5?) has issues with certain reponses being too small.

Firefox 2.0.0.6 seems to do that locking up thing. Maybe it''s just waiting for a newline character or something? But the socket connection is closed, so I would think it would stop, I dunno.


这是我可以访问的网站吗?
Is this a site I can access?


这篇关于firefox向后兼容性bug的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆