I was getting this in a reproducible way some months ago and all I had to do was move from the local LAN where it works to over an IPSec tunnel from the office which would be over the WAN where it did not work. The truncation result was more chaotic in my case, mostly Javascript files were chopped because looking at the resulting page the Javascript to decorate the jQueryUI buttons had not run. In some cases large jpg images were broken. For production I still front end with Apache and the problem goes away. What was puzzling at the time was different browsers got different results, probably timing differences between how they loaded referenced file resources that made up the page. In my case the page loads were under 5 seconds total. I concluded I would never run production under rocket so I did not press further. I still have the wireshark packet captures from then if you want them.
Ron On Tuesday, 26 June 2012 12:43:16 UTC-7, Massimo Di Pierro wrote: > > If you can reproduce. Chould you try wireshark to do a packet capture? I > would like to see what is going on. > Tim is a new dad and has not been responsive. I will try an attempt to fix > this myself (although I cannot repcoduce it) else we wil revert to > cherrypy. > > On Tuesday, 26 June 2012 07:04:15 UTC-5, Álvaro José Iradier wrote: >> >> Hi, >> >> I am developing an application that needs to return a big report page, >> with a lot of data. We were testing the application using the integrated >> rocket server, and the report was working correctly when accessing the app >> on the local network. >> >> However, when connection from the outside via a DSL router, making a NAT >> to the web2py http server, the response page gets truncated after about >> 15-30 seconds (could not determine an exact period). The browser stops >> receiving data, and the page is truncated. Capturing traffic with wireshark >> shows the remote end is finishing the connection (FIN flag set) before >> sending all data, but the Content-Length header was correctly set to a >> higher value. >> >> The problem dissapears when running web2py with lighttpd via FastCGI. >> >> The truncate problem also dissapears if instead of accessing directly to >> the web server, we make a SSH tunnel to the Linux machine hosting the >> web2py application, and requesting the report though the tunnel, but >> probably the SSH tunnel is retrieving the full page, then buffering it >> through the tunnel. >> >> Has anybody hit the same problem? It there a maximum response time for >> rocket server? I found there is a maximum request time, but the request is >> being processed quite fast, less than 1 second. The problem is *sending* >> the response, which is getting longer. >> >> Thanks. >> >> --
