-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTPClientRequest - multipart/form-data Support #32
Comments
There is currently no high-level implementation for this, so the request body would have to be composed manually. I initially thought there was an implementation, but that was just some e-mail composition code ("multipart/mixed", "multipart/alternative", "multipart/related") that we are using internally. The API of that isn't really suitable for use with the HTTP client, though, so it doesn't make much sense to take that. As for
Contributions here are certainly welcome! |
I made two initial PRs, both in their early stage of development. Between the original RFCs and Vibe's own architecture, there's a lot going on, so I wanted to get some early feedback to make sure I'm on the right path and not too far off track. |
Is it currently possible to use
HTTPClientRequest
to send requests with content-typemultipart/form-data
? An example use-case would be to send a request to an endpoint that takes a file as an upload.The protocol is described here in RFC 2388: https://datatracker.ietf.org/doc/html/rfc2388
An example endpoint that uses this protocol would be GitLab's
POST /api/v4/projects/{id}/uploads
endpoint: https://docs.gitlab.com/ee/api/projects.html#upload-a-fileIs this an area where contributions are desired? And if so, what is the intended interface for using this capability? I suspect the HTTPClientRequest::writePart() function is meant to be involved, but I'm not super clear what a simple invocation would look like.
The text was updated successfully, but these errors were encountered: