Well did you wait 300 secs or did it come immediately? because if you did then it is the webserver that cuts the
connectionbecause you have surpassed the timeout. Simply increasing the 300 value may work. however some browsers have
atimeout on their side too.
I believe that the problem is probably caused by something other than postgres, (it may be any number of things) just
tryswapping around a lot of different things and settings - try storing the file to disk instead - does that work? try
readingthe post input directly and see if it is all there? if it comes immediately - has it already transferred the 7
mb?try setting boobie-traps in your script - what is the size of the actual post? have you remembered to set the
appropriateenctype in the form ('multipart/form-data') there are simply too many things that can cause this. Try to
narrowthe problem down - and if it turns out to be postgres, then I do not know what the problem might be - somebody
elsehere might though. I just uploaded a 10mb file through http into postgres - no problem.
On 24 Oct 2001 07:23:59 -0700, qk22@gmx.co.uk (qk22) wrote:
> postgresql@envisity.com ("Aasmund Midttun Godal") wrote in message news:<20011024001923.22212.qmail@ns.krot.org>...
>
> I checked httpd.conf and found the "timeout" setting is 300, I tried
> again and the error message in netscape appears immediately as
> following:
> ______________________________________
> A network error occurred while netscape
> was sending data.
> (Network Error: Connection reset by peer)
>
> Try connection again
> ______________________________________
> I want to know if there are some configuration changes that can be
> made in order to enable the input of large text data though web
> server.
>
> Thank you
>
> qk22
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
Aasmund Midttun Godal
aasmund@godal.com - http://www.godal.com/
+47 40 45 20 46
