Thanks Majid

well there are Flash based on front end solutions e.g. SWFUpload, but it's not 
possible in Javascript. I think it's still important to have a server solution 
as well. I do agree though that it's kind of crazy to find out AFTER you upload 
a file, that the file was too big!

Brian

________________________________________
From: AOLserver Discussion [AOLSERVER@LISTSERV.AOL.COM] On Behalf Of Majid Khan 
[majidkha...@gmail.com]
Sent: 23 June 2011 14:34
To: AOLSERVER@LISTSERV.AOL.COM
Subject: Re: [AOLSERVER] Problem with file uploads larger than maxinput

I think if its possible in your case use the javascript and calculate the size 
of the upload file and return it right away if its  exceeds the limit this way 
you dont' need to worry about sending the request to the server, waiting for a 
while and ended up with nothing returned.

Regards,

Majid.

On Thu, Jun 23, 2011 at 5:16 PM, Fenton, Brian 
<brian.fen...@quest.ie<mailto:brian.fen...@quest.ie>> wrote:
Thanks Jim

I should have mentioned that there was nothing in the error log either.

So, how would you recommend I capture the fact that the uploaded file is larger 
than our limit, and feedback to the user?


thanks
Brian


________________________________________
From: AOLserver Discussion 
[AOLSERVER@LISTSERV.AOL.COM<mailto:AOLSERVER@LISTSERV.AOL.COM>] On Behalf Of 
Jim Davidson [jgdavid...@mac.com<mailto:jgdavid...@mac.com>]
Sent: 23 June 2011 13:47
To: AOLSERVER@LISTSERV.AOL.COM<mailto:AOLSERVER@LISTSERV.AOL.COM>
Subject: Re: [AOLSERVER] Problem with file uploads larger than maxinput

Hi,

The short answer is no, there's no access log entry although there may be a 
server log message buried in the chatter.

The reason is the access log is a "trace" that fires at the end of an HTTP 
connection and the request isn't a connection until all the content has been 
read and the data structures hooked up and passed over to a connection thread.  
In retrospect, transaction logging should be a lower-level built-in that can 
deal with logging these aborted transactions.

You can see what may be logged in the server log by looking at the LogReadError 
function at the end of nsd/driver.c, maybe a E_RRANGE, "max request exceeded".


-Jim




On Jun 23, 2011, at 6:04 AM, Fenton, Brian wrote:

> Hi
>
> When I upload a file larger than the maxinput I get the Firefox browser page 
> with a "the connection to the server was reset while the page was loading" 
> message. Looking in the access logs it seems to suggest that it doesn't even 
> hit the website as there is no log entry. A file smaller than the maxinput 
> uploads with no problems and everything is correctly logged. Increasing 
> maxinput allows the file to upload and also is everything is correctly logged 
> (so it's not a browser or network issue).
>
> I don't fully understand this - if there is no entry in the access log, does 
> this mean that I'm not even connnecting to AOLserver? As the success of the 
> upload is dependent on maxinput I imagine there is some sort of connection to 
> the server. Assuming there is a connection how can I log it or intercept it?
>
> Can anyone advise me on what to try? Ideally, I'd like to be able to capture 
> the fact that the uploaded file is larger than our limit, and feedback to the 
> user. Even more ideally, I'd like to be able to tell them BEFORE they upload. 
> :-)
>
> I've got the following settings in my config.tcl (this is AOLserver 4.5.1 but 
> also happens on 4.0.10 and on Windows version)
>
> set max_file_upload_mb        10
> set max_file_upload_min        5
> ns_section ns/server/${server}/module/nssock
>    ns_param   maxinput           [expr {$max_file_upload_mb * 1024 * 1024}] 
> ;# Maximum File Size for uploads in bytes
>    ns_param   maxpost            [expr {$max_file_upload_mb * 1024 * 1024}] 
> ;# Maximum File Size for uploads in bytes
>    ns_param   recvwait           [expr {$max_file_upload_min * 60}] ;# 
> Maximum request time in minutes
>
>
> --
> AOLserver - http://www.aolserver.com/
>
> To Remove yourself from this list, simply send an email to 
> <lists...@listserv.aol.com<mailto:lists...@listserv.aol.com>> with the
> body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: 
> field of your email blank.


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to 
<lists...@listserv.aol.com<mailto:lists...@listserv.aol.com>> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: 
field of your email blank.


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to 
<lists...@listserv.aol.com<mailto:lists...@listserv.aol.com>> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: 
field of your email blank.






--
AOLserver - http://www.aolserver.com/



To Remove yourself from this list, simply send an email to 
<lists...@listserv.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: 
field of your email blank.


--
AOLserver - http://www.aolserver.com/

To Remove yourself from this list, simply send an email to 
<lists...@listserv.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: 
field of your email blank.

Reply via email to