在doInterceptions方法里有对Warehouse.interceptors的判断

if (null != Warehouse.interceptors && Warehouse.interceptors.size() > 0){
      checkInterceptorsInitStatus();
      ......
}

而Warehouse.interceptors是在InterceptorServiceImpl#init里新线程里完成添加的

         IInterceptor iInterceptor = interceptorClass.getConstructor().newInstance();
         iInterceptor.init(context);

• Instead of holding implementations for each logging, tracing, metrics providers, establish interfaces.
• Be clear about it in docs
• Store implementations in... nested go modules? Separate project? To agree.

为了让 Component 更好, 我设计了这个奖励机制. 凡是满足以下的条件的 bug 都会奖励 25 元的奶茶钱. 钱虽然不多, 重在感谢

Bug 满足条件

• 必须是能复现的
• 必须是 Component 项目中的bug, 不能是其他第三方库的, Idea Plugin 不算在其中. 因为插件属于帮助性的工具, 出问题也不影响你们开发
• 必须是没有其他人反馈过的 Bug
• 必须是我认可的：首先如果真的是 bug, 我不会为了这点钱死皮赖脸不承认. 因为之前看下来, 很多 bug 都是用户自己配置有问题或者代码写的不对引起的, 并不是框架的问题. 所以这个是需要我来判断的. 当然了, 你足够了解 Component 的话, 你自己也会知道到底是不是 Component 的问题

所有发现 bug 受奖励的名单, 会持续更新(

⚠️ Is your feature request related to a problem? Please describe

Currently there is some inconsistency in having README in develop branch.
In case of adding some feature and its description into develop users see this description and think that this feature is available in the latest stable release, while it might be not released yet. Such situation happened recently.
Also, Chuc

What problem does this feature solve?

In the past, Brotli was not supported on nodejs servers.

If I understand correctly, this is now supported since a few months : nodejs/node#20458

This PR dropped support for Brotli : nuxt-community/axios-module#180

Maybe it's time to revert this BR because Axios is supporting it too : https://github.com/ax

It would be useful to see e.g avg message size for the frame.

If we want this then for AC:
Add histograms (optional):

• grpc_server_msg_size_received_bytes
• grpc_client_msg_size_received_bytes
• grpc_server_msg_size_sent_bytes
• grpc_client_msg_size_sent_bytes

It's useful model for extend the expiration automatically sometime.
I haven't found related infomation about this feature.
Would you consider to support this feature?

Currently the Forwarded header is overwritten. We should be standards compliant and append values instead to reflect the full path the request may have been proxied through.

https://github.com/vfaronov/httpheader looks good for this.

In order to make it easier to debug inflation exceptions in large apps, we should consider adding an API that provides the layout resource id that was trying to be inflated and possibly any other information that the app would like to tag the inflation request with.

Current docs shows this as an example:

const fetchRouter = new Router({
  strategies: ['fetch']
});

Which is wrong, since that argument should be the second one, not the first one.

A proper example would be:

const fetchRouter = new Router(
  {} , // interceptor options
  {
    strategies: ['fetch']
  }
);

ring-defaults' wrap-defaults adds the ring.middleware.content-type/wrap-content-type middleware by default (see https://github.com/ring-clojure/ring-defaults/blob/master/src/ring/middleware/defaults.clj#L27 and further occurences of :content-types)
Muuntaja's muuntaja.middleware/wrap-format will silently not do anything when ring's content-type middleware is also present.

Is it possibl

The extension popup window feels too small and the user has to scroll down to intercept/un-intercept multiple requests. This should be avoided.

Currently the UI looks like this:

We may need something like:

![screen shot 2018-08-22 at 6 22 03 pm]

See Early Termination in the Pedestal docs + part of the source

I think this kind of hook is something that's missing from Sieppari right now.