Arg, the problem is still there in Mozilla, but not in Chrome. Ajax can often be hard to debug.
On Dec 31, 12:48 am, weheh <[email protected]> wrote: > Hmmm, I'm not sure if I'm hitting that limit or not. I'll have to > check. > > Now, I just tested the behavior in mozilla with eclipse in debug mode > and saw the failure. But when I ran chrome outside of eclipse, the > failure wasn't there. So perhaps this is a timeout issue? > > On Dec 31, 12:39 am, mdipierro <[email protected]> wrote: > > >http://stackoverflow.com/questions/686217/maximum-on-http-header-values > > > On Dec 30, 11:36 pm, weheh <[email protected]> wrote: > > > > Is the a length limit to response.js? I've got a component response to > > > a form submission. The response is made of multiple parts: a, b, c and > > > d. Each part (a,b,c, or d) is a concatenation of multiple > > > jQuery("#some_id").html("some_response"); statements. The parts test > > > out ok individually, and when combined with one or two of the other > > > parts. But when all the parts are combined, the response.js fails to > > > update the target divs and the component with the submitted form fails > > > to update. > > > > I'm wondering if this is caused by a limit to the length of string > > > that can be passed via response.js? Seems unlikely, but I'm at a loss > > > as to what's going on. All the jQuery statements are terminated by a ; > > > \n, so together, they shouldn't create a syntax error. > >
