You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by "David Neuman (JIRA)" <ji...@apache.org> on 2017/08/21 17:20:00 UTC
[jira] [Created] (TC-544) TR should de-dupe Reponse Headers when
sending a Steering response.
David Neuman created TC-544:
-------------------------------
Summary: TR should de-dupe Reponse Headers when sending a Steering response.
Key: TC-544
URL: https://issues.apache.org/jira/browse/TC-544
Project: Traffic Control
Issue Type: Bug
Components: Traffic Router
Reporter: David Neuman
Assignee: David Neuman
Priority: Minor
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: *,*,*).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)