ContentType should be Content-type

Details

  • User impact:
    Low
  • Similar Issues:
    None

Description

Issue described, along with a work-around in this user forum thread:
http://www.nabble.com/HTTP-Transport%2C-ContentType%2C-Mule-2.1-td19999824.html#a19999824

Basically setting the the "contentType" attribute should change the "Content-type" HTTP header, but instead sets a "ContentType" header, which is not valid HTTP.

Workaround is to use a message properties transformer.

Issue Links

duplicates

Bug - A problem which impairs or prevents the functions of the product. MULE-3411 Http endpoint contentType element value gets ignored and overwritten with default value

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

No work has yet been logged on this issue.

People

  • Assignee:
    Ross Mason
    Reporter:
    Rick Otten
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: