This is about file uploading through servlets.
>If you think about how HTTP works, the client makes a request, then the
>server sends a response. The client doesn't expect or look for the
>response until the request has completed. So if the server decided the
>request is too large to process, what's going to happen? Either the
>server "eats" the request to generate a proper error message thus
>wasting bandwidth, or the server "hangs up" on the client while the
>client is sending the request. You're seeing the latter behavior.
Isn't this is a possible security hole. I mean if my server is going to go
on reading the bytes and storing them somewhere there is a possibility that
I might run out of disk space or the server might slow down. One option is
isolate the file upload servlet in a separate box.
What I am doing now is to have two limits on the file i.e., say 5 MB and 1
MB.
If the user sends a file between 1 and 5 MB an error message will be
displayed. If he tries to send a larger file, he will get the browser's
error message.
By the way, Netscape 4 shows "connection closed" error message whereas IE
shows
the "server could not be found" message.
Any suggestions.
Regards
Nagaraj.
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
