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

Allow Http accept header setting #112

christophd opened this Issue Jul 18, 2016 · 0 comments


None yet
1 participant

christophd commented Jul 18, 2016

Http client should support configuration setting for adding automatic accept header with default values. Usually the automatic accept header contains all supported content types coming from the underlying operating system which can be a very long list. The header is automatically added by Spring.

Citrus client components should have a setting for not adding this automatic header.

<bean name="customizedRestTemplate" class="org.springframework.web.client.RestTemplate">
    <property name="messageConverters">
        <util:list id="converter">
            <bean class="org.springframework.http.converter.StringHttpMessageConverter">
                <property name="writeAcceptCharset" value="false"/>

Default behavior should be to add the header as it has been before.

@christophd christophd modified the milestones: v2.7, SOMEDAY Sep 22, 2016

@christophd christophd modified the milestones: v2.6.2, SOMEDAY Nov 8, 2016

@christophd christophd added READY and removed BACKLOG labels Nov 8, 2016

@christophd christophd self-assigned this Nov 10, 2016

@christophd christophd added IN PROGRESS and removed READY labels Nov 10, 2016

@christophd christophd assigned christophd and unassigned christophd Nov 10, 2016

@christophd christophd added TO REVIEW and removed IN PROGRESS labels Nov 10, 2016

@christophd christophd removed their assignment Nov 10, 2016

@christophd christophd closed this Nov 10, 2016

@christophd christophd removed the TO REVIEW label Nov 10, 2016

christophd added a commit that referenced this issue Nov 11, 2016

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