Yes thats happen for me too seems that it is caused due to ssh tunnel is single connection where web request open multiple connections.
Try testing with a page with no external css/js and it will work fine. There may be work around for ssh-tunnel not doing multiple requests . On Tue, Nov 23, 2010 at 2:43 AM, G <[email protected]> wrote: > Hello, > I have a strange problem. My server is behind a fire wall so I must > use ssh tunnels to access web2py pages running on it. This works great > with the default webserver included with web2py. To achieve better > performance, I have now installed apache and got web2py working with > it after a few gotchas. Everything works fine on computers behind the > firewall. But now when I view the pages through the ssh tunnel (at > http://localhost:32197 where 32197 is the port that is tunneled > through ssh to the servers port 80), the pages do not seem to load > completely. Refreshing the page repeatedly shows that the page loads > to different points each time. Sometimes the page does load > completely, but most often not. It seems that the various static/.js > and .css files are often what fails to load all the way, though I've > seen the main content also fail to load. Is there perhaps some (very > short) timeout that is causing this somewhere? It would have to be > very short as the page loads only take a fraction of a second. I am > just testing with the basic welcome and admin apps. I have also > forwarded port 443 and find the same behavior there. > > Any ideas? > Thanks, > G
