From: Damien O'R. <da...@en...> - 2011-07-24 12:21:26
|
Hi, I upgraded my version of erlang on Mac OS x 10.6 from R13Bxx 32bit to R14B03 64bit. On the older version Yaws 1.9 was working fine ... except I couldn't upload a file greater than 2GB in size ... never threw an error, just didn't do it. After the upgrade (so I can upload > 2GB files) the server starts but whenever any file (even ones that worked before) is selected and submitted it throws a 'The connection was reset' error page for binary files, and it just shows the actual text of the upload.yaws file when a text file is submitted The following (or similar) appears on the command line (running with -i -T --debug) when a page is submitted *** CLI -> SRV *** New (nossl) connection from 127.0.0.1:51118 *** CLI -> SRV *** POST /upload.yaws HTTP/1.1 Connection: keep-alive Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Host: localhost:8102 Referer: http://localhost:8102/upload0.yaws User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:5.0.1) Gecko/20100101 Firefox/5.0.1 Cookie: _boss_session=1ba5362d9b134b36a8c130b6715df0df933d5bbf; _beepbeep_session_id_=fdb8b89029a357a363dca896df2ce2798601ef09 Content-Length: 110344870 Content-Type: multipart/form-data; boundary=---------------------------9849436581144108930470211272 Dnt: 1 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Accept-Encoding: gzip, deflate Accept-Language: en-us,en;q=0.5 *** SRV -> CLI *** HTTP/1.1 200 OK Server: Yaws 1.90 Date: Sun, 24 Jul 2011 11:43:34 GMT Content-Length: 2615 Content-Type: text/html *** CLI -> SRV *** Bad request Same yaws config file for both the older and newer versions. Are there any known gotchas either moving from that older version to newer, or from 32 bit to 64bit? Thanks Damien |
From: Michael F. <mic...@tr...> - 2011-07-24 19:50:11
|
Have you searched the mailing list archive? I had run into some issues uploading files myself and found a configuration setting that helps, but there was also a bug fix to the upload code by Steve around April. Here are the links I found from searching the mailing list for "upload"<http://sourceforge.net/search/index.php?group_id=45637&type_of_search=mlists&q=upload&posted_date_start=&posted_date_end=&form_submit=Search>, that will hopefully be helpful to you. They may not address your issue, but is worth a try. https://github.com/klacke/yaws/issues/38 http://sourceforge.net/mailarchive/message.php?msg_id=26215244 http://sourceforge.net/mailarchive/message.php?msg_id=24669658 Good luck, Michael |
From: Damien O'R. <da...@en...> - 2011-07-24 22:27:14
|
Thanks. I'd already set the partial_post size to 65536, and I should have tried a diff browser e.g. Chrome with the older version as apparently that doesn't have an issue with > 2GB files. I'd be interested to know where Steve Vinoski has put the option for making the file upload binary instead of list. Is it a per server setting? Would check the code but don't know where it might be. Odd thing is it was working OK for 13B, except for the 2GB limit, and I upgraded to 14B because of a comment by contrib for erlang who said a fix for the integer limit in list (where i thought the problem was) would be in the next release i.e. 14B03. But after the upgraded no uploads work as expected so I'll probably drop back and do some more testing with 13B Damien On 25/07/2011, at 5:21 AM, Michael Foley wrote: > Have you searched the mailing list archive? I had run into some issues uploading files myself and found a configuration setting that helps, but there was also a bug fix to the upload code by Steve around April. > > Here are the links I found from searching the mailing list for "upload", that will hopefully be helpful to you. They may not address your issue, but is worth a try. > > https://github.com/klacke/yaws/issues/38 > http://sourceforge.net/mailarchive/message.php?msg_id=26215244 > http://sourceforge.net/mailarchive/message.php?msg_id=24669658 > > Good luck, > Michael > > |
From: Steve V. <vi...@ie...> - 2011-07-25 01:05:01
|
On Sun, Jul 24, 2011 at 6:27 PM, Damien O'Rourke <da...@en...> wrote: > Thanks. > I'd already set the partial_post size to 65536, and I should have tried a > diff browser e.g. Chrome with the older version as apparently that doesn't > have an issue with > 2GB files. > I'd be interested to know where Steve Vinoski has put the option for making > the file upload binary instead of list. Is it a per server setting? Would > check the code but don't know where it might be. It's described in the PDF documentation here: http://yaws.hyber.org/yaws.pdf in section 4.4. In your code you call: yaws_multipart:read_multipart_form(Arg, Options) where Options is a list, and you can include the atom binary in the list to get your upload data in binary form. --steve |
From: Damien O'R. <da...@en...> - 2011-07-25 02:03:31
|
Steve, ah ... ok ... I had an earlier version of the PDF which had only this in that section First the easy case: Not YET Written ... ..... fill this in later ..... Should have downloaded the PDF with 1.9 Thanks Damien On 25/07/2011, at 11:04 AM, Steve Vinoski wrote: > On Sun, Jul 24, 2011 at 6:27 PM, Damien O'Rourke <da...@en...> wrote: >> Thanks. >> I'd already set the partial_post size to 65536, and I should have tried a >> diff browser e.g. Chrome with the older version as apparently that doesn't >> have an issue with > 2GB files. >> I'd be interested to know where Steve Vinoski has put the option for making >> the file upload binary instead of list. Is it a per server setting? Would >> check the code but don't know where it might be. > > It's described in the PDF documentation here: > > http://yaws.hyber.org/yaws.pdf > > in section 4.4. > > In your code you call: > > yaws_multipart:read_multipart_form(Arg, Options) > > where Options is a list, and you can include the atom binary in the > list to get your upload data in binary form. > > --steve |