Souen, We set the TimeOut at 180. But the backends also have to allow large uploads without throwing errors/timing out.
Rob On Thu, Dec 20, 2012 at 12:12 PM, Souen Boniface <[email protected]> wrote: > For the records and to avoid confusing anyone in the future having the > same issue, i finally did not manage to solve my problem with the `Client` > setting. > > Changing the Client setting value did not actually make upload of large > files work. Someone probably put some mushrooms in my cereals the other day! > > Cheers, > > Souen > > > > On Tue, Dec 18, 2012 at 4:39 PM, Souen Boniface <[email protected]> wrote: > >> OK, it seems to work if i increase the *Client* setting in the conf file, >> not the TimeOut setting. >> >> Is this the setting you guys also had to increase to enable large file >> upload ? :) >> >> Anyway, thanks to all! >> >> Souen >> >> >> >> >> On Tue, Dec 18, 2012 at 3:52 PM, Souen Boniface <[email protected]> wrote: >> >>> Hi, >>> >>> Thank you very much for your replies. >>> >>> We don't have set any TimeOut in the configuration file, which means >>> that the setting is set at its default value if i understand the doc >>> correctly. >>> The default value is 15 seconds according to the man page. >>> >>> I tried with a TimeOut set to 400 (which is clearly longer than the time >>> the upload request is taking) but we still have the 500 page when uploading >>> large files :( >>> Rob, Gareth, how high have you set your TimeOut setting to be able to >>> upload some 50MB files ? :) >>> >>> We didn't have set any MaxRequest either, so i guess this is set to its >>> default value "unlimited". So it shouldn't affect the issue. >>> >>> I'm not sure where to investigate, now :/ >>> >>> Thanks for your help, though :) >>> >>> Souen >>> >>> >>> >>> >>> >>> >>> On Tue, Dec 18, 2012 at 1:03 PM, Joe Gooch <[email protected]>wrote: >>> >>>> And/or the MaxRequest setting being set to something greater than 0 but >>>> less than your content size.**** >>>> >>>> ** ** >>>> >>>> Joe**** >>>> >>>> ** ** >>>> >>>> *From:* Rob Hicks [mailto:[email protected]] >>>> *Sent:* Tuesday, December 18, 2012 12:58 PM >>>> *To:* [email protected] >>>> *Subject:* Re: [Pound Mailing List] Error 500 when uploading large file >>>> **** >>>> >>>> ** ** >>>> >>>> I agree with Garrett. It's likely timeout issue. We routinely upload >>>> files as large as 50mb.**** >>>> >>>> ** ** >>>> >>>> rob h**** >>>> >>>> ** ** >>>> >>>> On Tue, Dec 18, 2012 at 10:40 AM, Garrett Hampton < >>>> [email protected]> wrote:**** >>>> >>>> What is your timeout set to? We had to increase ours for large files.* >>>> *** >>>> >>>> **** >>>> >>>> Garrett H.**** >>>> >>>> **** >>>> >>>> *From:* Souen Boniface [mailto:[email protected]] >>>> *Sent:* Monday, December 17, 2012 4:27 PM >>>> *To:* [email protected] >>>> *Subject:* [Pound Mailing List] Error 500 when uploading large file**** >>>> >>>> **** >>>> >>>> Hi all, >>>> >>>> We are using Pound in a project, and we are having trouble when >>>> uploading some file > 10MB. >>>> We get a 500 error: "An internal server error occurred. Please try >>>> again later." that seems to be served by Pound. >>>> >>>> Does Pound enforce an upload size limit or might that be because the >>>> request taking too long to complete ? >>>> >>>> Thanks for your help ! >>>> >>>> Souen BONIFACE**** >>>> >>>> ** ** >>>> ------------------------------ >>>> >>>> Best Rate Referrals >>>> >>>> This email and any files transmitted with it are confidential and >>>> intended solely for the use of the individual or entity to whom they are >>>> addressed. If you have received this email in error please notify the >>>> system manager. This message contains confidential information and is >>>> intended only for the individual named. If you are not the named addressee >>>> you should not disseminate, distribute or copy this e-mail. Please notify >>>> the sender immediately by e-mail if you have received this e-mail by >>>> mistake and delete this e-mail from your system. If you are not the >>>> intended recipient you are notified that disclosing, copying, distributing >>>> or taking any action in reliance on the contents of this information is >>>> strictly prohibited.**** >>>> >>>> ** ** >>>> >>> >>> >> >
