Could you provide some more details, like which REST service you are calling (if it is a publicly-accessible one), what is the request type (POST/PUT), some logs that show the exact error, etc.?
Also, have you tried the same REST calls with a non-vRO REST client (Postman/cURL/etc) to verify that they pass successfully (to rule out the possibility for this limitation to be related to the REST endpoint itself)?
The service is custom internal and using the squid web proxy but I don't know all of the details. I'm doing a post. It's working fine with curl and also some other folks have a perl script that they tested with. Both of those work. I'm gonna try some additional testing today with rest with some really large posts. I kinda stopped once I saw it working with what was breaking in vRO but maybe there is some variance in the request generated so I'll make sure the post is like 3000 characters and see if that causes an issue.
The plugin doesn't throw any errors its just on the receiving end its getting no data as soon as I bump the character count above that 1993 mark in the post. I get a web page back from the web proxy and this is the snippet about the error:
<p><b>Zero Sized Reply</b></p>
<p>Squid did not receive any data for this request.</p>
<p>Generated Tue, 15 Jan 2019 08:55:15 GMT by someserver.somcompany.com (squid)</p>
<!-- ERR_ZERO_SIZE_OBJECT -->
OK...just tried a request via curl with a 6000 character post and that worked fine.
Tested it in my 7.3.1 environment with a REST operations that does POST to run a workflow with a single string input parameter, passing it a string value of 3000 characters. Verified that the value of the same length is received in the workflow execution. Looks like everything works as expected.
ERR_ZERO_SIZE_OBJECT is an error returned by Squid web proxy so I guess something is wrong with its configuration.
Can you try a post with a json object? I can send you data that is blowing up for me if you like just let me know a good email address to drop it. Maybe its something in the serialization that is causing the issue?
Sure, can try with your data. Sent you an email via private message.
1 person found this helpful
Created a simple Spring REST service and tested with your data as a POST request body. Works fine.
Thanks! I guess it must be something on our end... really strange I can't break it though with a curl call.
I wanted to come back and update this thread. It looks like this was an issue on the server hosting the api with large requests over https. http works fine. Something for others to be aware of if you ever encounter such strange behavior.