Hi Tommi Not using SSL at this time. The failed uploads are over the internet but with relatively fast connections (High Speed DSL). Both the working server and the failing server are multicore and both run the same version (1.5.3-2). Failures occur with files as small as 30k but larger files guarantees failure ... but again, only on this one server and *only* from Linux browser clients. Using Windows FF or Windows IE always works which is odd.
What is the difference between these two client environments? A protocol issue? CR LF handling? little-endian vs big-endian? Keep in mind that even the failing server will allow uploading of tiny files from Linux clients. And the same server allows uploading of very large files from Windows clients. It is only Linux-Client + file of 30k+ that fails and only on this one server. We've tested many Linux and Windows clients just to be certain the problem is consistent. On 21/05/08 12:13 PM, [EMAIL PROTECTED] wrote: > Send Tntnet-general mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/tntnet-general > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Tntnet-general digest..." > > > Today's Topics: > > 1. Socket failed and dies on uploading files (Paul) > 2. Namespaces (Carlos Averett) > 3. Tntnet.jam (Eduardo Gurgel) > 4. Re: Socket failed and dies on uploading files (Tommi M?kitalo) > 5. Re: Namespaces (Tommi M?kitalo) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 20 May 2008 12:35:47 -0700 > From: Paul <[EMAIL PROTECTED]> > Subject: [Tntnet-general] Socket failed and dies on uploading files > To: [email protected] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi Tommi > > 3 issues: > > - uploading large files fails using Linux clients only > - socket failed error messages on one server > - upload iterator it != mp.end() true when should be false > > Scenario: > > I started trying to upload files to a tntnet application we are > developing and everything works fine on our testing server. But when we > installed on the production server everything worked except large file > (100K+) uploads (not that this is very large!). The testing server > permitted 1M+ easily. We are aware of the MaxRequestSize setting and we > have set this to zero (no limit) as well as other limits. Basically the > connection is killed with large uploads even if they are well below the > limit (or if there is no limit) and sometimes it requires a restart of > tntnet in order to upload even small files thereafter (puts tntnet in a > bad state, but only for uploads, otherwise the application operates > normally). > > It gets stranger: > > The upload problem *only* occurs when using Linux (Firefox and Epiphany > both tested and failed). Using Windows Firefox and IE can easily upload > 1M+ files, never fails. But a browser running on Linux always fails with > large files (but not with files under approx 30k). > > We noticed the tntnet log on the production server is generating many > "socket failed" errors. This is new. Previously we had no such errors. > These errors occur even without uploading files. Maybe this is related. > It comes from worker.cpp > > Again, no problem on our testing server (no socket errors and no problem > with file uploads) and it is only Linux browser clients accessing the > production server that have the problem. > > Running tntnet 1.5.3-2 on Debian Etch, Kernel 2.6.18-5 > > Code being used to write file (simplified): Also note, which I found > strange, it != mp.end() was true even if I was not uploading a file. So > I had to add the if ( it->getFilename() != "" ) as a work around. > > const tnt::Multipart& mp = pclRequest.getMultipart(); > tnt::Multipart::const_iterator it = mp.find( "pflUpload" ); > > if (it != mp.end()) > { > if ( it->getFilename() != "" ) > { > std::ofstream f(vtxFolderAndFile.c_str()); > std::copy(it->getBodyBegin(), it->getBodyEnd(), > std::ostreambuf_iterator<char>(f)); > > } > } > > > > ------------------------------ > > Message: 2 > Date: Wed, 21 May 2008 09:04:45 +0000 (UTC) > From: Carlos Averett <[EMAIL PROTECTED]> > Subject: [Tntnet-general] Namespaces > To: [email protected] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=us-ascii > > Hello, > > I'm looking at switching over from PHP to TNTNet for a lot of things. As > such, > I'm planning on porting my application framework over as well. It includes a > lot of things - from the world's most paranoid session handler, to encryption > resistant to cryptanalysis, secure uploads, tag clouds, etc. > > What is the best way to go about making components for re-use (by myself, or > others)? Does TNTNet offer something like namespaces for components? > > > > > > > ------------------------------ > > Message: 3 > Date: Wed, 21 May 2008 09:48:28 -0300 > From: "Eduardo Gurgel" <[EMAIL PROTECTED]> > Subject: [Tntnet-general] Tntnet.jam > To: [email protected] > Message-ID: > <[EMAIL PROTECTED]> > Content-Type: text/plain; charset="iso-8859-1" > > Message: > > Added tntnet application server support, from Eduardo Gurgel. > *Source*: http://svn.boost.org/trac/boost/changeset/45606 > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Tntnet-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tntnet-general
