I have this same behavior on multiple web2py servers. If a large file is being uploaded using a SQLFORM or downloaded using the default download controller, over HTTPS, the entire web server becomes unresponsive until the transfer is completed or cancelled. However, I have no issues uploading/downloading the same file over HTTP, which can also take several minutes to complete, but the web server is still responsive during those transfers.
I am using the one-step deployment with Apache and a wildcard certificate (RapidSSL). Would switching to nginx or cherokee give better performance for https file transfers, or is this likely an issue with the SSL certificate format? Or if the file transfers over HTTPS are too CPU intensive, am i better off setting up multiple servers and a load balancer? Thanks! Dave R -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
