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

Set content-type when sending HTTP notifications #249

Closed
pierre opened this issue Jan 14, 2015 · 1 comment
Closed

Set content-type when sending HTTP notifications #249

pierre opened this issue Jan 14, 2015 · 1 comment

Comments

@pierre
Copy link
Member

pierre commented Jan 14, 2015

See https://groups.google.com/forum/#!msg/killbilling-users/bdVl7hdV69Y/Wa98SsSbCJ8J.

@ntherning
Copy link

I've been bitten by this as well. Trying to get Spring MVC to accept the request from KillBill. Spring will assume application/octet-stream when no Content-Type is set in the request. And the MappingJackson2HttpMessageConverter which converts the request body to JSON by default only can read application/json. Workaround was to configure Spring MVC with a second MappingJackson2HttpMessageConverter which supports application/octet-stream.

@pierre pierre added this to the Release-0.13.6 milestone Mar 18, 2015
@pierre pierre self-assigned this Mar 18, 2015
@pierre pierre closed this as completed in 242875e May 5, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants