Skip to content
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

Httpjson input: Allow specifying POST JSON body #768

Closed
stanch opened this issue Feb 29, 2016 · 6 comments · Fixed by #5074
Closed

Httpjson input: Allow specifying POST JSON body #768

stanch opened this issue Feb 29, 2016 · 6 comments · Fixed by #5074

Comments

@stanch
Copy link

stanch commented Feb 29, 2016

It would be convenient to be able to specify JSON body for POST requests. I guess just providing JSON as a string works, but if it is to be separated by keys, non-string values should be supported (unlike with the GET parameters).

@sparrc
Copy link
Contributor

sparrc commented Feb 29, 2016

sure, could you separate this into two separate issues though?

@stanch stanch changed the title Httpjson input: Allow specifying POST JSON body and disabling SSL verification Httpjson input: Allow specifying POST JSON body Feb 29, 2016
@stanch
Copy link
Author

stanch commented Feb 29, 2016

Done!

@guige
Copy link

guige commented Jun 29, 2017

How can input body for http request. I had input body from readme example, but return error.

@danielnelson
Copy link
Contributor

@guige We try to reserve GitHub Issues for actionable bug reports or feature requests. Please ask general questions at the InfluxData Community site.

@guige
Copy link

guige commented Jul 7, 2017

@danielnelson I resove it use httpjson, because i use httprespose.😭

@nmjensen
Copy link

This feature would be very useful. I've currently worked around it by calling curl from the exec plugin, but as I'm running Telegraf in the alpine based docker image - it doesn't include curl so I need to install it using apk whenever it's updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants