I only can reproduce it on the production server. The fail comes about 2 seconds aftehr when the upload begins (and with my connection is impossible to upload 1.2 mb in 2 seconds), but the uploading screen doesn't changes, is like the firefox is waiting for a response.
2011/9/20 Massimo Di Pierro <massimo.dipie...@gmail.com> > Is this reproductible? How long does the upload take? > > On Sep 19, 10:45 am, demetrio <dgzabal...@gmail.com> wrote: > > Hi, i'm having the next traceback when I try to upload a file in the > > production server: > > > > Traceback (most recent call last): > > File "/srv/web2py/gluon/main.py", line 442, in wsgibase > > parse_get_post_vars(request, environ) > > File "/srv/web2py/gluon/main.py", line 276, in parse_get_post_vars > > request.body = copystream_progress(request) ### stores request > > body > > File "/srv/web2py/gluon/main.py", line 144, in copystream_progress > > copystream(source, dest, size, chunk_size) > > File "/srv/web2py/gluon/fileutils.py", line 366, in copystream > > data = src.read(chunk_size) > > File "/usr/lib/python2.6/socket.py", line 377, in read > > data = self._sock.recv(left) > > timeout: timed out > > > > The problem comes when I try to upload a 1.2mb zip file. If I upload a > > text file with less mb, there is no problem. And there is no problem > > with the web2py own server. Only in the production machine. > > > > The machine is running web2py 1.98.1 under Debian GNU/Linux 6.0.2 > > (squeeze) with python 2.6 > > > > Does anybody knows whats happening? > > > > Thanks in advance >
