In our codebase, we push RequestContext and immediately run some code with try-with-resources.
For example:

try (SafeCloseable ignored = ctx.push()) {
    logger.trace(decorate(msg));
}

If RequestContext provides run(Runnable) or call(Callable) we can reduce boilerplate code and simplify it.

ctx.run(() -> logger.trace(decorate(msg));

This is inspired by g

有同学经常提问针对application/x-www-form-urlencoded类型的post请求，在使用分流插件后获取不到post参数，大部分都是因为配置不当或者对Nginx相关知识点理解不清晰导致的。

下面介绍一个相关issue的正确配置：

1. nginx.conf里配置一个upstream:

upstream business_upstream {
        server 127.0.0.1:8003;
}

2. 然后配一个server用来作为business_upstream的服务提供者:

server {
        listen 8003;
        server_name localhost 127.0.0.1;
        access_log ./log

Is your feature request related to a problem? Please describe.

As observed during #261, users can accidentally set timeouts inconsistently. A concrete example is that one can set a User facing timeout lower than any backend timeout, such that requests may fail early.

Describe the solution you'd like

We should provide some sanity checking to prevent unintended timeout behavior.

Bug:
The iothub connection string is present as part of docker inspect output.

Expectation:
Perhaps something like docker secret (https://docs.docker.com/engine/reference/commandline/secret/) or similar should be used to avoid the credentials appearing in plain text in docker inspect.

Description:

Following error is logged during startup, after changing the userstore type as database in deployment.toml.

org.wso2.carbon.databridge.agent.exception.DataEndpointLoginException: Cannot borrow client for ssl://172.17.0.1:9711.
	at org.wso2.carbon.databridge.agent.endpoint.DataEndpointConnectionWorker.connect(DataEndpointConnectionWorker.java:145) ~[org.wso2.carbon.data

doctests will help us catch any stale examples in the documentation, in case the examples break due to changes in code.

The following need to be resolved for doctests to work:

1. The outputs also have to be written down in the documentation

• Typical response objects are huge (will take up a lot of space).
• Responses are unique and can't be tested against.

2. Our examples invoke calls

transformRequest only fires if its a method that can have a body. This is misleading, as it's very common to perhaps want to tweak headers or something on an outgoing request before it gets to the destination server.

The solution is "use" instead of "transformRequest", but I was banging my head on this today.

One of the features added in PR #629 was the ability for users to specify per-user volume mounting by specifying KERNEL_VOLUME_MOUNTS and KERNEL_VOLUMES values in the env stanza of the api/kernels POST request's json body. We need to document an example of how that would be accomplished. It could be as simple as taking the example from #629

This issue came up during the review of PR #7

The file kuranet.conf seems to contain most of the parameters for the network configuration, but I haven't found the exhaustive list of parameters we can put in it and the associated keywords.
This could be very helpful to provide a default network configuration for a particular application.
Wat is the precedence between kuranet.conf and snapshot and they have to be in sink at some point.

Un

代码设置 StaticResurceType：
g = new Gateway();
g.HttpOptions(options =>
{
options.StaticResurceType = "txt;xml;zip;jpg;css;png;htm;woff;svg;gif;woff2;js;html;jpeg;ico;rar";
}
g.Open();
woff 文件显示 403错误。
GET http://..../__system/layuiadmin/layui/font/iconfont.woff?v=230 net::ERR_ABORTED 403 (No permission)
如果使用 HttpConfig.json 则一切正常。

看了代码，只有在实例化HttpApiServer时才会初始化，后续设置StaticResurce