Brian Devins

Unfortunately right now that's not possible for us. We are at 3.14.9 because we require it's Java 7 support.

Believe me I understand the frustration with the Java 7 support. If we shaded okhttp would that solve the problem for you?

What version of webflux are you on? It's possible this is an issue that re-emerged with changes to reactor and reactor-netty, or we never fully fixed it but parts of...

Yes, that mismatch would be expected since we have an alternate implementation for netty that covers 4.1+ Thanks for the version, that will help triage the issue

Hi @gokhanoner thanks for the report. Would you be able to help us reproduce this issue by providing a when clause for one of our tests that produces this issue:...

@milanaleksic unfortunately this does not exist yet in the Java library. Would a list of http hosts to not send to work for you?

Ok, good to know. Would a list of allowed hosts work? IE: only send the headers to listed hosts?

1) We are aware of this timing discrepancy, we haven't been able to address this yet but it is on our radar. As for suitable for production, if those ~200microseconds...

Assuming this is using spring-boot you would probably have to configure it differently. I can't find an example of that configuration though. See: https://docs.spring.io/spring-framework/docs/current/reference/html/web-reactive.html#webflux-server-choice > For Undertow, Spring WebFlux uses...

The first issue is because b3 IDs need to be 16 characters[^1] hex encoded. The equivalents of what you posted above are: `000C5311AF5ABF11`, `000000BB202ED685` We will have to look into...