Thanks for this amazing tool!

The issue is as following:
If there are two virtual hosts (Server blocks) serving two host names or subdomains:

sd1.domain.com
sd2.domain.com

When the configuration is generated using the nginxconfig and if HTTP to HTTPS redirect is enabled following server block gets generated for each host:

--- For virtual host 1
# HTTP redirect
server {
  

Let's support at least reading "b3" header from a single string, most commonly traceid-spanid-1
It would also be nice to support optionally writing this, especially in message providers or others with constrained environments.

Expected behavior

As discussed on openzipkin/b3-propagation#21 and first implemented here: https://github.com/openzipkin/brave/blob/master/brave/src/main/java/bra

非常感谢大家对 SOFAStack 开源的关注和支持，这是我们前进最大的动力。

收集目的

• 了解 SOFAStack 的使用场景以便更好的规划技术路线
• 聆听社区的不同声音，让 SOFAStack 变得更好
• 吸引更多的开源爱好者参与贡献，共同打造 SOFAStack

收集方式

请按如下参考格式回复本 Issue 进行登记：

* 公司/组织名称：蚂蚁金服
* 地点：中国杭州
* 网址：http://www.antfin.com
* 使用组件及场景：全套金融级分布式中间件
* 联系方式：[email protected]

展示

我们会定期同步信息至「Awesome SOFA」的用户列表中。

服务

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

currently "option forwardfor" cant't be unset, so there is no way to enable it in the default section and disable it in a particular frontend