Spring-cloud-sleuth: The HTTP header line does not conform to RFC 7230 and has been ignored.

[gasperlf]

Describe the bug
I'm using sleuth to trace my request but when i call from a microservice another I'm getting 400 bad request.

CONFIG
spring.sleuth.propagation-keys=X─B3─TraceId,X─B3─ParentSpanId,X─B3─SpanId,X─B3─Sampled

2019-12-16 16:27:53.497 INFO [xxx-service,,,] 939 --- [nio-8081-exec-3] o.apache.coyote.http11.Http11Processor : Error parsing HTTP request header
Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.
java.lang.IllegalArgumentException: The HTTP header line [xB3SpanId: d57f94dc9ccdfd58] does not conform to RFC 7230 and has been ignored.
at org.apache.coyote.http11.Http11InputBuffer.skipLine(Http11InputBuffer.java:953)
at org.apache.coyote.http11.Http11InputBuffer.parseHeader(Http11InputBuffer.java:816)
at org.apache.coyote.http11.Http11InputBuffer.parseHeaders(Http11InputBuffer.java:563)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:311)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:834)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1417)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)

[spencergibb]

Closing in favor of https://stackoverflow.com/questions/59360384/the-http-header-line-does-not-conform-to-rfc-7230-and-has-been-ignored

Please don't cross post.

[marcingrzejszczak]

I'm sorry but i can't help you with an issue having such a description.

Which version of sleuth are you using, who is throwing an exception and how, why do you think sleuth is the problem.

Please provide meaningful details

[gasperlf]

the sleuth version is 2.1.0 and I think sleuth is the problem because he is inject the headers in the response

[spencergibb]

If we're conversing here, please close stack overflow issue.