The binding cert has the site id and environment in the cn but not the
binding id


On Wed, Jan 15, 2014 at 3:36 PM, David Strauss <notifications@github.com>wrote:

> In src/filecache.c:
>
> > + * We do this by turning the default LOG_INFO level which is passed in
> > + * to enhanced logging to LOG_NOTICE.
> > + */
> > +struct curl_slist* enhanced_logging(struct curl_slist *slist, int log_level, int section, const char *format, ...) {
> > +    va_list ap;
> > +
> > +    // If we are injecting errors, we can trigger enhanced logging by decrementing
> > +    // the log level (LOG_INFO -> LOG_NOTICE)
> > +    if (inject_error(filecache_error_enhanced_logging)) {
> > +        log_level -= 1;
> > +    }
> > +    if (logging(log_level, section)) {
> > +        char *instance_identifier = NULL;
> > +        char msg[81] = {0};
> > +        slist = curl_slist_append(slist, "Log-To-Journal: true");
> > +        asprintf(&instance_identifier, "Instance-Identifier: %s", get_instance_identifier());
>
> It certainly can uniquely identify the client, as we do for events. I'm
> not sure if the binding ID is included, though. In any case, I'd prefer to
> have a "User Agent" option for FuseDAV that Chef sets in the config file to
> something including the binding ID.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/pantheon-systems/fusedav/pull/138/files#r8917474>
> .
>



-- 
Ray Thompson
Pantheon Engineer