the server or proxy not found

i'm trying to test this product.
I'm using asp and using the multipledescriptions test

i'm getting an error
the server or proxy not found

what could be causing an error like this?

ok so i change that to point to the persistsaspupload.asp
but not i get image uploaded encountered some problem please contact your webmaster

how can I debug this to see where the problem is?

i get both of those errors; i have the showdebug as true, yet it still doesn't give me a debug window for those two errors. it does give me a debug window for other ASP related errors.

i am only running into these errors when i am attempting to upload files 500 megs or larger

please help

I am running rails and having a same problem.

"The server or proxy not found." I am testing out your product and not getting anywhere.

Can you help me out?

Thanks for the reply.

It's a small image file. I guess I don't have right setting for uploader for my rails app. Do you have any idea why?

Is it because it can't find the folder called gallery? (whatever I named to the upload folder)

Or Is there some kind of configuration that I am missing?

Thanks much

I am getting the "The server or proxy not found" error again with rails 2.1.0 version.

I had to disable the "protect_from_forgery" from rails app.

I still get this error and on top of that i get this error .
"No route matches "/uploads/gallery/BasicDemo/upload.rb" with {:method=>:post}"

any ideas guys?

I wonder if someone has simple demo of updated ruby on rails app using your product.

thanks

Edited by user Friday, August 15, 2008 3:42:34 AM(UTC)  | Reason: Not specified

(back to this problem...)

No sir, there is no maximum post request length. can upload full 2 gig file on super fast connection [internal network], no problem. Problem happens at more realistic speeds like DSL, and Cable.

Timeout: Correct me if I am wrong, but the Timeout would only apply in the actual SAVE portion of the upload, yes? in my most recent upload attempt (using Mac/firefox image uploader 4.x) I am getting this error at differnt points in the upload itself (actual file size: 800megs, bombed out at; 35megs, 745kg, 22megs, 107 megs). Since the file has not as yet actually been touched by a server side script, how can timeout apply?

Oh - Before anyone mentions upgrading, Version 5 came out not long after we bought the product, since we haven't managed to get version 4 to work reliably, i am convinced that the product should do what it was advertised to do with the version we have and if it takes an upgrade to do what it is supposed to do in the first place, then that upgrade should be free.

Thank you.

Edited by user Thursday, November 13, 2008 10:56:19 PM(UTC)  | Reason: Not specified

Thank you for your reply -

My server Timeout for the saving page is (and has been for a year) 16 hours. I am pretty sure that that should be long enough. But if it is not long enough, how can that be the issue when sometimes (as stated before) the upload failes after only a couple 100 kbs and sometimes after 100 megs? there is no consistency there.

If it got to the same general point in the upload and failed each time, i would agree with you. but it does not.

As to uploading seperatly - i can't. it's all one file. we deal with real size super large graphics - e.g. the types used on Fleet Trucks. these things are bloody huge and can actually reach 2gig in one file. there is no choice to "send them seperately"

however, I do have FilesPerOnePackageCount = 1 which should in effect be the same isn't it?

Thank you
Scott

Dmitry -

Yes, i've doen alot of looking into this in the last couple of days and found that what you say here is correct though, the error message is unique to Aurigma which made it very hard to troubleshoot. - you may want to consider putting more information in the error or adding it to your help file... actually an error section in general would be nice with your help documentation.

As it turns out, the uploader is losing connection with the server and then the backend script which does the saving of the file throws an error on the first attempt to read from the form. Now the problem is figuring out how to get the server to play nice with the connection.

the test machine is using an aircard - but we've had this same problem with DSL and Cable too. I am using IIS and ASP Classic (i've noticed that Microsoft specifically says that files over 100 megs really shouldn't be sent by way of HTTP - and makes a strong point of this for ASP.NET.

Can anyone suggest which failSave program is the best? i've tried ASPForm, ASPUpload, ABCUpload... and all of them fail in the same way. :\

Also, would it be worth setting up a PHP catcher page? if so, would apache be less inclined to fail?

Thanks