jalanstrom
Occasional Contributor
Joined 9 years ago
User Profile
User Widgets
Contributions
Re: Content-Transfer-Encoding type quoted-printable adds equals (=) symbols web service cannot process
nmrao wrote: Nothing set for Part (for the attachment). Do you see anything in the drop down? Are you using this step in a test case? There are no options available from the Part drop-down list. This POST request is a test step in a test case. The problem is not with the file attachment part, it is with the length of the content in the part named documentmodel in the POST request (see original post for link to entire content of the request). As mentioned in the original post, when the length of the aforementioned part exceeds a certain length, the Content-Transfer-Encoding type is automatically set to quoted-printable by SoapUI. The quoted-printable format is what causes the '=' characters to be placed in the request as line endings as shown in the request content. As a result of the '=' characters in the request, the REST service cannot read the JSON content of the documentmodel part.Content-Transfer-Encoding type quoted-printable adds equals (=) symbols web service cannot process
Due to the length of the content in the request, SoapUI Open Source is automatically setting the Content-Transfer-Encoding type to printed-quotable. Link to request text: https://gist.github.com/jalanstrom/ed71aa1c8d32a59ece07b6e063f9e041 Unfortunately, the application is expecting JSON content in that part of the request, so it's rejecting the request because of those equals (=) signs. Link to response text: https://gist.github.com/jalanstrom/a6d6ea336e992c956b0c9200cfcdd7d9 When using Content-Transfer-Encoding type is 7bit, the request completes fine (link to request text: https://gist.github.com/jalanstrom/e20273c4322eb8c7c31d3a6199fa49be). But as soon as I go over a certain content limit, SoapUI is automatically changing the type to quote-printable. Unfortunately I have yet to find any way to modify the Content-Transfer-Encoding type to something suitable (base64? binary?) that won't add the extra characters that drive my REST service crazy. Thanks for any help!!
