Issue Summary

Automation can add a second content-type header to the outgoing web request.

Steps to Reproduce

1. Create a rule with an outgoing web request.
2. Add the Content-type header application/json to the action configuration
   1. Note: The lower-case "t"

Expected Results

Automation does not automatically add a second heder

Actual Results

Two headers get added causing the recipient to reject the request

Workaround

If using application/json, remove the content-type header from the action config and let automation handle it. Or, use the correct case: Content-Type