Jean-Charles Sisk

Shows up with `--loglevel=silly` but, it is, after all, a silly amount of logging.

We were bitten by this yesterday, too. Published a new build at around 3am EST in the [always-attempt-gzip](https://github.com/krakenjs/kappa/tree/760cf6e4c4119641abdded1768f8e36696dd7be6) branch. Published as `1.0.0-rc.14` (also in the `rc` dist-tag, installable as `npm...

> Looks like npm is not aware of your published version That's just the `latest` dist-tag. ``` sh $ npm info kappa dist-tags { latest: '1.0.0-rc.11', rc: '1.0.0-rc.14' } ```

> I don't see that errors by the way, but just sudden slowness of all requests. slowness by way of client? That could be the client retrying on error (the...

Looking at the linked npm thread, it looks like they are now correctly parsing the `accepts-encoding` header. This was not the case when I hurriedly made the change last night...

We log out using the standard hapi logging events, consumable by [good](https://github.com/hapijs/good). The versions we use are way out of date but they still work. [Here's an example of how...

> Even though npm said they fixed all the changes, the older version of Kappa still doesn't work. Yup. It's due to the fact that in the version of the...

Also, I'll be leaving this issue open until I strip out the header munging. We technically support gzip now but, with npm now respecting the `accept-encoding` header, we're not actually...

> Yes, I did. I put it in the header Authorization: Bearer . Hello @lvarayut. a csrf token is not an auth token—it won't work as a bearer token. You'll...

No worries. Glad it worked out. :grinning: