Hi Anil Yes, it works for us, we're using it. For the first part, basic/digest auth, there is a patch that got applied to the 4.8 branch that uses both, but it doesn't look like it got forwarded to the 4.9 branch. I pinged octo on IRC, hopefully this will be fixed soon.
I'm not sure what webserver you're using, but the write_http plugin uses PUTVAL-style plaintext data in the body of the POST. Depending on what webserver you're using, it might not be in QUERY_STRING. In the rails app where we use it, for example, the data is in `request.body`. I hope this helps, if not, come find me in the IRC #collectd channel. Paul On Fri, Feb 12, 2010 at 10:41 AM, Anil <[email protected]> wrote: > Paul, just CC'ing you on this. Is this plugin supposed to work? > I could be interpreting this wrong but liburl expects CURLOPT_POSTFIELDS > data to be properly formatted, perhaps with the key=value pairing. > > Is this why it doesn't work? (of course I hacked it to send some dummy data > but it didn't work though... so I am sure I must be wrong.) > > > On Fri, Feb 12, 2010 at 1:21 AM, Anil <[email protected]> wrote: >> >> I am having trouble using the write_http plugin. On the web server, there >> is nothing in the QUERY_STRING environment variable. I tried both with basic >> and HTTP digest (I changed the code to use basic). >> >> Looking at the code, curl_easy_perform() returns with 0. There are no >> errors. >> >> Does the HTTP auth plus the POST variables get sent with the same request? >> I see the Authorization credentials but not the data. collectd is in fact >> reporting that it is capturing all the data and sending it. >> >> Thanks > > _______________________________________________ collectd mailing list [email protected] http://mailman.verplant.org/listinfo/collectd
