in reply to Beating the system

What kind of bandwidth do you have and do you see different file sizes if someone with a faster or slower connection than you tries an upload?

If so, and you're seeing errors like 'CGI.pm: Server closed socket during multipart read (client aborted?).' in your error logs (you are checking your error logs, right?), then you might be running into Apache's TimeOut or something similar.

A workaround for such (or possibly something else to try) is to fork() your own server for the duration of an upload.

    --k.


Replies are listed 'Best First'.
Re: Re: Beating the system
by mikeirw (Pilgrim) on Sep 29, 2002 at 18:38 UTC

    I'm personally testing from a machine that's on dial-up, but I've had another person test it with a broadband connection, and he received the same error. The error is a generic 500, and unfortunately, pair Networks does not allow access to the Apache error logs.

    I've setup the script to test for errors issued by CGI.pm, and I'm not seeing anything there. Testing the script on my own machine, I'm able to transfer multi-MB files without a hitch.

    Thanks to all who've provided suggestions. I'll give them a go, and post a resolution if I ever get one.

[reply]
      Use CGI::Carp so that you can get the error message in the browser, if it's a Perl error:

      use CGI::Carp qw(fatalsToBrowser);

      Trying to debug a CGI without access to STDERR is needlessly difficult.

      -sam

[reply]
[d/l]

In Section Seekers of Perl Wisdom