jiewang-2023 opened a new issue, #11355: URL: https://github.com/apache/skywalking/issues/11355
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no similar issues. ### Apache SkyWalking Component OAP server (apache/skywalking) ### What happened We used dapr to send the tracing data to Skywalking OAP in zipkin format, and found that the HTTP status code responded by Skywalking OAP was not 202, but 200. The official Zipkin protocol specifies returning a 202 status code. If the Dapr component determines that the status code is not 202, it determines that the sending failed. zipkin official http protocol format https://zipkin.io/zipkin-api/#/default/post_spans  ### What you expected to happen I used the curl command to test and found that Skywalking oap responded with a 200 status code, and we expected the status code to be 202  It is recommended to refer to the openzipkin repo https://github.com/openzipkin/zipkin/blob/master/zipkin-server/src/main/java/zipkin2/server/internal/ZipkinHttpCollector.java ### How to reproduce Push zipkin format data to Skywalking OAP's zipkin data receiving interface (http://{ip}:9411/api/v2/spans) curl --location 'http://ip:9411/api/v2/spans' --header 'Content-Type: application/json' --data '[ { "timestamp": 1695376149000000, "duration": 1570, "traceId": "5c818da0ee3b151e4568c56935063d72", "id": "f2bbd1c4511ad87a", "name": "/v1.0/metadata", "kind": "CLIENT", "localEndpoint": { "serviceName": "hello-tracing" }, "tags": { "dapr.api": "GET /v1.0/metadata", "dapr.protocol": "http", "dapr.status_code": "200", "otel.library.name": "dapr-diagnostics", "service.name": "hello-tracing" } } ]' ### Anything else _No response_ ### Are you willing to submit a pull request to fix on your own? - [ ] Yes I am willing to submit a pull request on my own! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@skywalking.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
