Cherokee Web Server

Eric S. Johansson | 2 May 2006 00:40

limits in uploading files

is there any limit in uploading files through CGI's?  For a project of 
mine where people upload CD and DVD length files (yes, it's legit, to be 
disclosed when we go live), I'm finding that I can only upload 126 MB 
worth of data before it fails.  I'm really confused if it's a problem of 
mine or something inherent within Cherokee.  Additionally, it looks like 
a CGI program is terminating (timeout??) because I'm not seeing my "I'm 
finished transferring" log message.  Come to think of it, someone 
uploading a 90 MB file over his cable modem failed before a complete as 
well which would give a small amount of credence to the timeout theory.

I'm running Cherokee 0.5.3 on ubuntu 5.10

headers

Eric S. Johansson | 2 May 2006 04:46

Re: limits in uploading files

Eric S. Johansson wrote:
> is there any limit in uploading files through CGI's?  For a project of 
...

> well which would give a small amount of credence to the timeout theory.

I changed CGI_timeout from 65 to 6500 and the amount of data uploaded 
before a failure almost doubled (200 MB) and I think, if I am 
interpreting logs correctly, the CGI ran for about 10 minutes.

I'll check again in the morning when I'm more awake.

headers

David Moreno Garza | 26 May 2006 08:34

Re: limits in uploading files

Eric S. Johansson wrote:
> I changed CGI_timeout from 65 to 6500 and the amount of data uploaded 
> before a failure almost doubled (200 MB) and I think, if I am 
> interpreting logs correctly, the CGI ran for about 10 minutes.
> 
> I'll check again in the morning when I'm more awake.

Any success?

--

-- 
David Moreno Garza <damog <at> damog.net>   |  http://www.damog.net/
		   <damog <at> debian.org>  |          GPG: C671257D
 Kumbia King: King of Kumbia.

headers

Eric S. Johansson | 26 May 2006 15:20

Re: limits in uploading files

David Moreno Garza wrote:
> Eric S. Johansson wrote:
>> I changed CGI_timeout from 65 to 6500 and the amount of data uploaded 
>> before a failure almost doubled (200 MB) and I think, if I am 
>> interpreting logs correctly, the CGI ran for about 10 minutes.
>>
>> I'll check again in the morning when I'm more awake.
> 
> Any success?
> 

couldn't quite figure if the failure was server or browser side but it 
wasn't a timeout problem, it was a resource problem.  One of the two 
sides keeps the file in memory before processing at and when you run out 
of resources, it dies.  It might be server-side but I really don't know. 
  Instead I'm slicing the file into chunks and uploading chunks for 
reassembly.  One of those "bypass the problem entirely" scenarios.

Right now I'm wrestling with authentication issues.  I wish they hadn't 
screwed up the http authentication definitions and allowed the CGI or 
server to remove authentication credentials when necessary.  But I have 
something that works with cookies using a technique outlined by bright 
people at MIT and all I need to do now is build and authentication 
database (yet again)

---eric