Reputation: 269
I have a docusign account, where I am creating an envelope of multiple/single documents and trying to send them through "Connect" to a particular endpoint/url after signing of the documents is done.
Now I have two applications for the endpoint url. The first application is a Rails 2.3.1 app in which I get all the params including byte streams of the files sent through docusign. This works fine.
The second application is a Rails 4.2.2 with ruby 2.2.2 . Now in this application, when I receive the request from the docusign, the request does not contain any params.
Can any one tell why there is difference in the behavior between Rails 2.3.1 and Rails 4.2.2.
Please Note in both the cases , the request is a POST request.
Update:
We have deployed a sample Rails 4 app on Heroku. Below is the link: https://aqueous-harbor-4271.herokuapp.com/docusign/consume which can be used to test a POST request that docusign sends through connect api. Just set up the connection endpoint as the above URL. It just renders the incoming request parameters in json as response.
Upvotes: 3
Views: 203
Reputation: 1132
Vipul said, "The issue has been fixed. It was related to Rails 4 stack where in it truncates the request parameters if the request method is POST and content type is application/xml. No issue with docusign."
I'm putting the answer here so this doesn't show up as an unanswered question when searching Stack Overflow.
Upvotes: 2