You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 28, 2024. It is now read-only.
The HttpClientRequest Rest engine already leverages org.apache.http.HttpEntity in HttpClientRequest#execute for the items supported via StringEntity, but misses an extremely cheap chance for wider support via is HttpEntity-> r.entity = entity
Due to the lack of open classes, it is current required to clone HttpClientEngine, HttpClientRequest & HttpClientResponse (plus ext functions on Rest.post) in order to support generic HttpEntity support.
In my use case, I have a single call requirement (application login) that involves multipart. Rest provides all the support I need except this.
With the engine/request/response cloned, I am now able to leverage the Apache clients MultipartEntityBuilder
The text was updated successfully, but these errors were encountered:
The
HttpClientRequest
Rest engine already leveragesorg.apache.http.HttpEntity
inHttpClientRequest#execute
for the items supported viaStringEntity
, but misses an extremely cheap chance for wider support viais HttpEntity-> r.entity = entity
Due to the lack of open classes, it is current required to clone
HttpClientEngine
,HttpClientRequest
&HttpClientResponse
(plus ext functions onRest.post
) in order to support generic HttpEntity support.In my use case, I have a single call requirement (application login) that involves multipart. Rest provides all the support I need except this.
With the engine/request/response cloned, I am now able to leverage the Apache clients
MultipartEntityBuilder
The text was updated successfully, but these errors were encountered: