submitForm fails for large PDF

[jojoshua]

We are using the JavaScript submitForm method to submit the form to a specified URL. The reason we do this is to send the PDF to our server. This works fine for most PDFs but larger ones are failing without any error given. Here is what the code looks like.

var return_msg = submitForm({ cURL: "urlToPost", cSubmitAs: "PDF"});

app.alert(return_msg); <- returns true

Is there any way to use submitForm for large files?

[try67]

I think the problem is most likely with the server, not the client. What are you using to receive the file on the back-end?

[jojoshua]

My wish is that it is the server, but can't seem to find issue with the server configuration.  It is asp.net WebAPI service that it submits to. We setup extended tracing and found that no requests were even hitting the server. Also made sure the request thresholds could hold up to 2gb files.

[try67]

I'm not too familiar with asp.net but I would also suggest you look into the max upload file size parameter. I have had similar problems with PHP-based services in the past, so I'm guessing it's a similar situation with ASP.

[try67]

Another option is a connectivity issue on the user's end that causes a time-out on the server if the upload takes too long, or the connection might break in the middle of the upload, causing the file to be dumped entirely.

[jojoshua]

I did find one piece of information in c:\windows\system32\LogFiles\HTTPERR on the server

It has a record with the item that failed showing HTTP/1.1 GET [url] - 1 Timer_EntityBody DefaultAppPool

I'm wondering why this shows GET rather than POST.

[Joel Geraci]

Can you share the PDF?

[jojoshua]

Unfortunately, I can't release the file. I could try to create a test file. Knowing that you were able to use this method for large PDFs is helpful. Were you in the range of 100s of MB?

[jojoshua]

I was reading that Timer_EntityBody error indicates that IIS did not receive any data from a client request and the request timed out. Client requests with large content length headers can cause this error. Could there possibly be an Acrobat setting for the Web Plugin that can be changed?

[Joel Geraci]

My 3D PDF files can be well over 300MB. My backend is a Windows server but it was running Apache as the web server and the application is PHP. I've never tried a PDF embedded in IE before though. My client is Chrome which doesn't use the Acrobat plugin so I need to set up my PDFs to be submitted through Acrobat or Reader. 

[Test Screen Name]

It's quite common to run into cases where people, seeing a facility, push it not just beyond what was tested but what was conceived. I'd say you are about 100 times larger than the largest Adobe conceived. Frankly I'd be amazed if it worked.

[Joel Geraci]

I'll have to agree. I've sent HUGE 3D PDF files to my server and not had any fail... after I increased my file upload size limit which was defaulted to 2Mb.

[jojoshua]

What was your backend? Is it possible that network configuration or IE settings cause this to break?

[Joel Geraci]

If the file is open in IE, try using a fully qualified URL and submitting the file from Acrobat.