Contributions
Re: REST-POST-application/octet-stream - ERROR:Exception in request...
Today I learned that enabling 'adds Expect-Continue header to outgoing request' in HTTP settings of SoapUI is the solution for the problem I initially reported. I hope this info helps other users that have the same problem.5.8KViews1like0CommentsRe: REST-POST-application/octet-stream - ERROR:Exception in request...
No I did not find a solution, for this specific combination. I'm convinced that this is a bug in the SoapUI software or 3rd part component. However I'm not a paying customer, so other then post it on the forum I cannot get additional support. I hope that since you also reported the problem, the people at smartbear get convinced that the problem is caused by a bug and not by something else.7.6KViews0likes0CommentsRe: REST-POST-application/octet-stream - ERROR:Exception in request...
I come to this conclusion(bug in SoapUI or 3rd part component used by SoapUI) for 3 reasons 1) As I already mentioned in ealier replies I can post successfully (still using digest authentication) in caseI don't attach the file, but post the binary file INLINE, then I don't get the error anymore... However including the binary file inline give me other problems because SoapUI encodes the binary file as if it was text.... So yes I post successfully by otherways, but I can't really call this a success if the file posted becomes unreadable because Soap encodes the binary file inline as text... If someone can tell me how to nclude a binary file inline that is not encoded as text.... However it would be so much easier to attach the file... 2) the error generated incase I POST with digest authentication and with file attached is a client-error(on SoapUI side), not a server error 3) in case I use a curl command to POST the file attached with digest authentication I have no problems at all, this proves there is no error on the server side So I suggest to try it yourself, to POST a file attached application/octect-stream (REST) with digest authenication or maybe you can tell me how to POSTa binary file inline that is not encoded as text....7.7KViews0likes3CommentsRe: REST-POST-application/octet-stream - ERROR:Exception in request...
No, so far I didn't find another way of posting the same successfully. As I already posted, incase Iinclude the binary file inline, then I get other problems because SoapUI encodes the binary file as if it was text.... If someone can tell me how to youinclude a binary file inline that is not encoded as text.... or if the soapUI bug would get resolved... (then I might even consider buying a license....)7.7KViews0likes5CommentsRe: REST-POST-application/octet-stream - ERROR:Exception in request...
Thank for answer. Meanwhile I analyzed the problem some more and came to the conclusion that the error is probably caused by a SoapUI bug. I think the error occurs because I use digest authentication in combination with a REST post request with a file attached. In this combination SoapUI doesn't retry after receiving the answer: 401 Unauthorized with the Digest realm and nonce values in the header In case I repeat my test, but instead of doing a REST post request with a file attached (still using digest authentication) I don't attach the file, but I post the binary file INLINE, then I don't get the error anymore. However including the binary file inline give me other problems because SoapUI encodes the binary file as if it was text.... Conclusion: I can't succussfully do a REST post request with application/octet-stream file in the body of the http-request in combination with digest authentication7.8KViews0likes7CommentsREST-POST-application/octet-stream - ERROR:Exception in request...
In case I do REST http request POST, and I attach to the request an image file, I modified the content-type of the attachment to application/octet-streamand the Media Type of the request is also application/octet-stream. see screenshot attached that illustrates the request note that the request uses digest authentication as well I'm using SOAPUI 5.2.1 I get an ERROR:Exception in request: org.apache.http.client.ClientProtocolException Wed Dec 09 11:20:14 CET 2015:ERROR:org.apache.http.client.ClientProtocolException org.apache.http.client.ClientProtocolException at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:822) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754) at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport$Helper.execute(HttpClientSupport.java:233) at com.eviware.soapui.impl.wsdl.support.http.HttpClientSupport.execute(HttpClientSupport.java:323) at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.submitRequest(HttpClientRequestTransport.java:290) at com.eviware.soapui.impl.wsdl.submit.transports.http.HttpClientRequestTransport.sendRequest(HttpClientRequestTransport.java:220) at com.eviware.soapui.impl.wsdl.WsdlSubmit.run(WsdlSubmit.java:119) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: org.apache.http.client.NonRepeatableRequestException: Cannot retry request with a non-repeatable request entity. at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:611) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:454) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820) ... 11 moreSolved8.3KViews0likes10Comments