Contributions
Re: endpoint cannot be selected for rest requests?
Thanks! This did not help me exactly, because it was there, but I needed to change the name of the "service" in the xml. <con:service type="REST" name="Test1"> was the name of the original ressource and the other environments had: <con:service type="REST" name="http://https://wss-${#Project#tpEnv}.abc.com"> which was the value of the endpoint and not the name of the service. After changing it to Test1 (Name of the service, I know it could be better) it works and everything is present. Thanks for guiding me to the correct place in the XML ;)7 years agoPlace ReadyAPI QuestionsReadyAPI Questions5.6KViews0likes0CommentsJSON too long in REST Request (POST)?
Hi there, I searched the internet and the community to find a proper solution but didn't find anything about that. We have an interface which receives a lot of data and parameters. It is a REST interface with a POST Method. In the Header I send the "Content-Length", which is about 26.000 characters, but Ready API cuts it off at around 10.000 characters (Seeing the raw request and count the characters there). Using the same Requests in Postman, it works fine and nothing is cut off, so basically it is working. Is there any way to increase the maximum length in ReadyAPI? E.g. raise some values in the vmoptions? Thanks in advanceSolved8 years agoPlace ReadyAPI QuestionsReadyAPI Questions3KViews0likes1Comment