Skip to content

Add Content-Type header when sending JSON to /api/v2/spans#1

Closed
timhabermaas wants to merge 1 commit intomtth:masterfrom
timhabermaas:fix-missing-content-type-jaeger
Closed

Add Content-Type header when sending JSON to /api/v2/spans#1
timhabermaas wants to merge 1 commit intomtth:masterfrom
timhabermaas:fix-missing-content-type-jaeger

Conversation

@timhabermaas
Copy link
Copy Markdown

Without the Content-Type Jaeger (tested using version 1.18) responded with "Unsupported Content-Type":

> curl -XPOST -d @foo2.json http://localhost:9411/api/v2/spans
Unsupported Content-Type

Without the Content-Type Jaeger (tested using version 1.18) responded with "Unsupported Content-Type":

    > curl -XPOST -d @foo2.json http://localhost:9411/api/v2/spans
    Unsupported Content-Type
@timhabermaas
Copy link
Copy Markdown
Author

timhabermaas commented Jun 15, 2020

This fix should be verifiable by using Jaeger's all-in-one Docker image (https://www.jaegertracing.io/docs/1.18/getting-started/#all-in-one) and pointing Zipkins settingsHostname to localhost and settingsPort to 9411.

With the Content-Type set all seems to be working fine when sending data to Jaeger. Including tags and annotations (called events in Jaeger):

Screen Shot 2020-06-15 at 22 28 48

serras added a commit to serras/tracing that referenced this pull request Jul 14, 2020
@mtth
Copy link
Copy Markdown
Owner

mtth commented Nov 12, 2020

Thanks for the PR @timhabermaas and apologies for the slow reply. I wasn't getting notifications from this repo and am just going through the PRs now. I think this was fixed by #3.

@mtth mtth closed this Nov 12, 2020
serras added a commit to serras/tracing that referenced this pull request Nov 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants