woof will start and handle HTTP requests successfully, but when actually trying to upload a file to the end-user it will crash with the following dump :-
$ woof -s
Now serving on http://IPADDR:8080/
HOSTNAME - - [05/Sep/2011 11:00:47] "GET /woof" 200 -
[Errno 32] Broken pipe
Connection broke. Aborting
----------------------------------------
Exception happened during processing of request from ('CLIENTIP', 47979)
Traceback (most recent call last):
File "/usr/lib/python2.7/SocketServer.py", line 284, in _handle_request_noblock
self.process_request(request, client_address)
File "/usr/lib/python2.7/SocketServer.py", line 310, in process_request
self.finish_request(request, client_address)
File "/usr/lib/python2.7/SocketServer.py", line 323, in finish_request
self.RequestHandlerClass(request, client_address, self)
File "/usr/lib/python2.7/SocketServer.py", line 641, in __init__
self.finish()
File "/usr/lib/python2.7/SocketServer.py", line 694, in finish
self.wfile.flush()
File "/usr/lib/python2.7/socket.py", line 303, in flush
self._sock.sendall(view[write_offset:write_offset+buffer_size])
error: [Errno 32] Broken pipe
----------------------------------------
According to our ArchLinux friends http://aur.archlinux.org/packages.php?ID=46323 this seems to be caused by some side-effect of forking a child process to handle the file upload; using the patch from npouillard to make woof single-threaded http://paste.pocoo.org/show/363409/ is successful.
Applying this patch is not ideal, as it removes capability from the product (i.e. multiple simultaneous client downloads) but on the other hand it will at least be able to upload something instead of nothing!
The relevant patch in the ArchLinux tarball is woof-nofork.patch which, as the OP says, removes some functionality.
There is also a proposed patch in FreeBSD that may be worth a look:
http://