Skip Menu |

This queue is for tickets about the Document-eSign-Docusign CPAN distribution.

Report information
The Basics
Id: 121502
Status: open
Priority: 0/
Queue: Document-eSign-Docusign
People
Owner: Nobody in particular
Requestors: jonleigh1960 [...] gmail.com
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Tue May 02 19:00:51 2017 jonleigh1960 [...] gmail.com - Ticket created
Subject: requestSignatureFromDocument giving "400 Bad Request" error with PDF files over about 5 pages long
Date: Wed, 3 May 2017 01:00:19 +0200
To: <bug-Document-eSign-Docusign [...] rt.cpan.org>
From: "Jon Leigh" <jonleigh1960 [...] gmail.com>
This is urgent. I am ready to go 'live' and suddenly have run into a brick wall. Module version/distribution: I am running the very latest distribution, installed from CPAN today: Document::eSign::Docusign 0.06. Perl version: perl, v5.10.1 (*) built for x86_64-linux-thread-multi Operating System vendor and version (by running the command uname -a) : Linux 404494-web1.portology.com 2.6.32-431.29.2.el6.x86_64 #1 SMP Sun Jul 27 15:55:46 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux ERROR MESSAGE : The hashref returned, when converted to json, is as follows:- {"error":"400 Bad Requst"} First of all, I know that the PDF document I am trying to send is FINE because I have sent it successfully using the API Explorer in the Docusign Sandbox. I have had my API interface up and running and everything has been fine WITH A TEST PDF DOCUMENT of just 1 page. The actual document I want to send is 18 pages long - and has to be signed on the last page. I sent and got a '400 Bad Request' error. To cut a long story short, if I just "cut" my original PDF down to its first 5 pages then it sends. 7 pages: I get the "400 Bad Request" error. Anything more: Ditto. Wondering if my PDF was corrupt, I have validates it online at https://www.pdf-online.com/osa/validate.aspx and it is NOT corrupt. Just to be 100% sure, I used the DocuSign API Explorer to do the Document Send. IT WORKED NO PROBLEM. The 18 page version isn't even a large file: It's only about 230k. Therefore the only explanation can be that the sendRequest module simply is unable to handle anything other than a very small PDF file with very few pages. Jon Leigh
  Tue May 02 22:48:25 2017 tyler [...] seraph-net.net - Correspondence added
Subject: Re: [rt.cpan.org #121502] requestSignatureFromDocument giving "400 Bad Request" error with PDF files over about 5 pages long
Date: Tue, 2 May 2017 19:48:08 -0700
To: bug-Document-eSign-Docusign [...] rt.cpan.org
From: Tyler Hardison <tyler [...] seraph-net.net>
Check that any proxy servers between you and the remote server limit request sizes. Seems like a request size issue..? But the limit on the modules underneath (LWP:Request) are unlimited. On Tue, May 2, 2017 at 4:00 PM, Jon Leigh via RT < bug-Document-eSign-Docusign@rt.cpan.org> wrote: Show quoted text
> Tue May 02 19:00:51 2017: Request 121502 was acted upon. > Transaction: Ticket created by jonleigh1960@gmail.com > Queue: Document-eSign-Docusign > Subject: requestSignatureFromDocument giving "400 Bad Request" error > with PDF files over about 5 pages long > Broken in: (no value) > Severity: (no value) > Owner: Nobody > Requestors: jonleigh1960@gmail.com > Status: new > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=121502 > > > > This is urgent. I am ready to go 'live' and suddenly have run into a brick > wall. > > > > Module version/distribution: > > I am running the very latest distribution, installed from CPAN today: > Document::eSign::Docusign 0.06. > > > > Perl version: > > perl, v5.10.1 (*) built for x86_64-linux-thread-multi > > > > Operating System vendor and version (by running the command uname -a) : > > Linux 404494-web1.portology.com 2.6.32-431.29.2.el6.x86_64 #1 SMP Sun Jul > 27 > 15:55:46 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux > > > > ERROR MESSAGE : > > The hashref returned, when converted to json, is as > follows:- {"error":"400 Bad Requst"} > > > > > > First of all, I know that the PDF document I am trying to send is FINE > because I have sent it successfully using the API Explorer in the Docusign > Sandbox. > > > > I have had my API interface up and running and everything has been fine > WITH > A TEST PDF DOCUMENT of just 1 page. > > > > The actual document I want to send is 18 pages long - and has to be signed > on the last page. > > > > I sent and got a '400 Bad Request' error. > > > > To cut a long story short, if I just "cut" my original PDF down to its > first > 5 pages then it sends. > > > > 7 pages: I get the "400 Bad Request" error. > > > > Anything more: Ditto. > > > > Wondering if my PDF was corrupt, I have validates it online at > https://www.pdf-online.com/osa/validate.aspx and it is NOT corrupt. > > > > Just to be 100% sure, I used the DocuSign API Explorer to do the Document > Send. IT WORKED NO PROBLEM. > > > > The 18 page version isn't even a large file: It's only about 230k. > > > > Therefore the only explanation can be that the sendRequest module simply is > unable to handle anything other than a very small PDF file with very few > pages. > > > > Jon Leigh > > >
  Tue May 02 22:48:25 2017 The RT System itself - Status changed from 'new' to 'open'