On Thursday, December 15, 2016 at 2:11:57 PM UTC-8, Dave S wrote: > > When uploading a file from one of our Windows clients, we sometimes find > this in the web2py.log file: > > [...] > > File "/home/ec2-user/web2py/web2py-2.14.6/gluon/rocket.py", line 1766, > in write > self.send_headers(data, sections) > > > File "/home/ec2-user/web2py/web2py-2.14.6/gluon/rocket.py", line 1750, > in send_headers > self.conn.sendall(b(header_data)) > > > File "/usr/lib64/python2.7/socket.py", line 228, in meth > return getattr(self._sock,name)(*args) > > > error: [Errno 32] Broken pipe > > > Is this basically a timeout because the end of transfer wasn't detected > properly? Or is something going wrong with preparing and sending the > response? > > With a quick look at line 1750, I see it follows something about closing the connection. Is that "close" as in book-keeping, or "close" as socket code thinks the connection is closed?
/dps -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
