-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Feature request: Client: Post with content receiver #1818
Comments
@Green-Sky thanks for the feedback. I didn't implement those because I simply don't need those. I don't expect any large response body when issuing any HTTP requests in my use cases except GET requests... You can easily add such a POST method. Could you send a pull request to implement the method that you need with a unit test? Then, I'll review and merge it. Thanks! |
@Green-Sky I definitely have interest in this feature as well; if you roll a PR let me know otherwise I'll take a stab at it myself. Thanks. |
@jmont-dev feel free to implement it, i am currently occupied with something else. |
I have a usecase where
client.Post()
is called with a small body and the server response is a very lengthy string/json, where acontent receiver
would make sense.And after all the difference between http
GET
PUT
POST
etc on the protocol level is just that, a word. 😏The text was updated successfully, but these errors were encountered: