|
I am running a server which holds packages for Emacs's The problem is, if there are multiple packages available from my repository, the TCP connection to the server remains open during the installation. The steps are,
The problem is that -- for some larger packages -- the connection times out because of the I tried running a local instance of the Apache server, but it doesn't seem to work. Looks like nginx is the proxy and has a 65 second timeout. It looks like in the system wide Apache configuration, asked 05 Dec '11, 11:00 milkypostman |
|
Keep alive connections do not persist because of the nature of the nginx proxy. Apps 'in front' of the proxy have HTTP/1.1 and have a set keepalive for 3 seconds. Apps 'behind' the proxy have HTTP/1.0 and it does not have keepalive connections. Is it possible to use another protocol like SSH? If not directly than for testing you may want to try an SSH tunnel. That would allow you to rule nginx out as a possibility without having to change the account. If bypassing nginx does work we can open a port with a Dedicated IP address. answered 10 Dec '11, 01:52 johns I tried with an ssh tunnel directly to the port of a django install configured to only serve up static files and it seems to work great. So it must be the nginx proxy. I'm not sure all what a dedicated IP implies and I don't really want to pay for it. I'll have to think about it.
(15 Dec '11, 12:25)
milkypostman
|
In our control panel, what app type are you using to serve the packages?
I've tried a number of different ones: Static/CGI/PHP, Static only (no .htaccess), and I also tried a Django/mod_wsgi one where I changed all the apache settings to enable long keep alive.
also, sorry it took me so long to reply, I didn't have notifications setup.