From: Joe W. <jo...@gm...> - 2010-11-16 22:25:47
|
Hi Adam, Thanks for your reply! > I just did a quick search, and sandbox3.js at line 174, looks like it > may produce this error. It looks to me like you get this error if the > AJAX request to the server to call compile.xql, throws some of > exception. > > Do you have Chrome? If you switch on the developer tools in Chrome and > enable Resource Tracking, then you should be able to see the error > returned by compile.xql, which could shed some hints. Although it may > be possible to just find this error in exist.log as well? I used the Live HTTP Headers plugin for Firefox, and the error returned was: HTTP/1.1 413 FULL head Content-Length: 0 Connection: close Server: Jetty(7.1.5.v20100705) Based on this and a little trial and error, I think the error was caused by the sheer length of the POST. The upper limit is somewhere around 4150 or 4250 characters before a Shadow Error is triggered. I'm not sure if there's any way to catch this response in sandbox's code so that a more descriptive error can be displayed, but now at least we know what caused it! Thanks, Joe |