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
Hi,
As far as I can see support for multipart/form-data is only available for HTTP requests (both for the client and server side).
Any opinion/plans about adding client and server support also for HTTP responses? This would be handy for all those cases where a HTTP server needs to "atomically" return one or more files (application/octet-stream) along with associated metadata (e.g. JSON, XML), without resorting to encoding the files, e.g. as BASE64 within a JSON field, since this latter solution bloats the response and adds considerable processing and memory overhead...
Thanks
The text was updated successfully, but these errors were encountered:
Sure, but so do you think it would make sense to implement something like this?
I am still not sure the HTTP standard allows to use such a content-type within a response...
I haven't investigated if it's possible to implement the feature, yet. Do you know any HTTP libraries which support such a feature? If so, I'll take a look at how those libraries implement it. I personally don't need it on my projects at this point though.
Hi,
As far as I can see support for multipart/form-data is only available for HTTP requests (both for the client and server side).
Any opinion/plans about adding client and server support also for HTTP responses? This would be handy for all those cases where a HTTP server needs to "atomically" return one or more files (application/octet-stream) along with associated metadata (e.g. JSON, XML), without resorting to encoding the files, e.g. as BASE64 within a JSON field, since this latter solution bloats the response and adds considerable processing and memory overhead...
Thanks
The text was updated successfully, but these errors were encountered: