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

Use charset from http headers to parse the payload #511

svettwer opened this Issue Oct 12, 2018 · 0 comments


None yet
2 participants
Copy link

svettwer commented Oct 12, 2018

User story
As a citrus user, I want Citrus to use the charset I've specified in my http header to parse the payload, so that I don't have to configure the charset separately.

Additional context
When a application type like Content-Type:application/x-www-form-urlencoded;charset=UTF-8 is specified in a header, Citrus would ignore the delivered charset and use the charset configured for citrus. It's important to have a fallback strategy that is consistent to the current implementation.

More details in #500 and #510


@christophd christophd added this to the v2.8 milestone Oct 19, 2018

@christophd christophd referenced this issue Nov 30, 2018


Fix public API breaking changes in 2.7.x #549

9 of 9 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment