I think the condensed is better but it'll need to change post 2.0 to accomodate for logging the number of bytes read in the body of a titan request (and it's weird to hardcode a zero there.) 2.0 will ship with the legacy logging style thus.

upon an unexpected EOF, tls_error() returns NULL, so log the real reason iomux returned -1.

otherwise it enters an infinite loop where it tries to read, return zero, and tries again...

the parameters need to be added at the end of the path, not at the end of the URL.