Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Content-Type isn't send to Interceptor #1614

Closed
khrm opened this issue Jul 17, 2023 · 4 comments · Fixed by #1615
Closed

Content-Type isn't send to Interceptor #1614

khrm opened this issue Jul 17, 2023 · 4 comments · Fixed by #1615
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@khrm
Copy link
Contributor

khrm commented Jul 17, 2023

Expected Behavior

Content-Type should be sent to Interceptor when making a POST request.
Some of web frameworks in other languages expect this header.

Actual Behavior

At present, when making a POST request to the interceptor, we don't set Content-Type header.

@khrm khrm added the kind/bug Categorizes issue or PR as related to a bug. label Jul 17, 2023
@khrm
Copy link
Contributor Author

khrm commented Jul 17, 2023

/assign @khrm

@khrm
Copy link
Contributor Author

khrm commented Jul 17, 2023

/cc @ggallen

@khrm
Copy link
Contributor Author

khrm commented Aug 18, 2023

@ggallen Do we need this? How did you solve this? Was there some issue with the interceptor that you have written?

@ggallen
Copy link

ggallen commented Aug 18, 2023

Yes, this is an actual bug. To work around it we have a filter that is adding the required header.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants