ASP页面中的响应缓冲区限制超出错误 [英] Response Buffer Limit Exceeded error in ASP page

查看:205
本文介绍了ASP页面中的响应缓冲区限制超出错误的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

错误: 响应对象错误'ASP 0251:80004005'

Error: Response object error 'ASP 0251 : 80004005'

超出响应缓冲区限制

执行ASP页导致响应缓冲区超过其配置的限制.

Execution of the ASP page caused the Response Buffer to exceed its configured limit.

我用这段代码解决了这个问题,但问题没有解决

I use this code to solve this issue but problem is not solved

<% Response.Buffer=False %>
<%
do while not objrs.eof
response.flush
objrs.movenext
loop
%>

Plz,请帮助我解决此问题

Plz, help me to solve this issue

推荐答案

如果将Response.Buffer设置为false不能解决问题,那么您一次调用Response.Write会写入过多数据.

If setting Response.Buffer to false isn't helping then you are writing too much data via a single call to Response.Write.

永远不会真正关闭缓冲.每次对Response.Write的调用都将把内容写入ASP的缓冲区中.使用Response.Buffer = False时,ASP将在每次调用Response.Write之后自动刷新缓冲区.

Buffering is never really turned off. Each call to Response.Write will place the content written in ASP's buffer. With Response.Buffer = False ASP will automatically flush the buffer after each call to Response.Write.

因此,即使传递给Response.Write的字符串将超过缓冲区大小,即使使用Response.Buffer = False,仍然仍有可能出现缓冲区超出"错误.

Therefore even with Response.Buffer = False it is still possible to get a "Buffer exceeded" error if the string passed to Response.Write would exceed the buffer size.

如果您拥有服务器,那么我建议您保留缓冲区,而在IIS管理器中增加ASP响应缓冲限制".如果您使用的是托管服务,那么将通过Response.Write发送的所有大数据分成较小的块,例如128KB至1MB.

If you own the server then I would recommend leaving buffer on and instead increase the ASP "Response Buffering Limit" in IIS Manager. OTH if you are using a hosting service then split up any large data being sent via Response.Write into smaller chunks say between 128KB to 1MB.

这篇关于ASP页面中的响应缓冲区限制超出错误的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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