[TC-544] TR should de-dupe Reponse Headers when sending a Steering response.

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: Traffic Router
• Assignee: David Neuman
• Reporter: David Neuman
• Created: 21/Aug/17 17:19
• Updated: 21/Aug/17 17:19

Description

If you have a steering delivery service configured and the subordinate delivery services have the same Traffic Router Response Headers defined, you will get multiple Headers in your response.
For example if you set CORS header on each of the subordinate DSs (e.g. Access-Control-Allow-Origin: *), you will end up with 3 CORS headers in your response.
This could cause an issue with some clients which will try to chain the headers together (e.g. Access-Control-Allow-Origin: ,,*).