Hi Joey, On Sun, Aug 16, 2009 at 06:25:19PM -0400, Joey Hess wrote: > I eventually figured out that apache was throwing a 302 redirect, and > collectd doesn't follow this redirect. I think it should either > follow, or log that it is failing to get the apache scoreboard.
the documentation of libcurl, the library used for HTTP access, is a bit
fuzzy on the issue. If I understand it correctly, though, the library
follows redirects by default (unless the FILE or SCP schema is used). It
even sends along authentication information if the redirect points to
the same host.
I think this is basically sane behavior, so I think it'd be best to just
report to the user when not following a redirect.
> 127.0.0.1 - - [16/Aug/2009:18:17:40 -0400] "GET /server-status?auto HTTP/1.1"
> 302 296 "-" "collectd/4.6.3"
> 127.0.0.1 - - [16/Aug/2009:18:17:50 -0400] "GET /server-status?auto HTTP/1.1"
> 302 296 "-" "collectd/4.6.3"
> 127.0.0.1 - - [16/Aug/2009:18:18:00 -0400] "GET /server-status?auto HTTP/1.1"
> 302 296 "-" "collectd/4.6.3"
> 127.0.0.1 - - [16/Aug/2009:18:18:10 -0400] "GET /server-status?auto HTTP/1.1"
> 302 296 "-" "collectd/4.6.3"
^
I'm a bit surprised not to see a username in your log entries, I have to
admit, but this may actually be the expected behavior of Apache
(redirect ⇒ no authentication ⇒ no username).
Could you please provide your configuration of the “Apache” plugin
(spare the password, of course) and ideally the headers returned by
Apache?
Regards,
-octo
--
Florian octo Forster
Hacker in training
GnuPG: 0x91523C3D
http://verplant.org/
signature.asc
Description: Digital signature
