[
https://issues.apache.org/jira/browse/TS-4510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15317623#comment-15317623
]
ASF GitHub Bot commented on TS-4510:
------------------------------------
GitHub user shukitchan opened a pull request:
https://github.com/apache/trafficserver/pull/697
TS-4510: support multiple header with same name
Currently ts_lua plugin does not handle well when the request or response
contains multiple header with the same name.
We either retrieve the last value of first value of these headers and when
we set new value to the header, we only change the first one and leave the rest
there still.
@jpeach , pls help to take a look. I think I can refactor later on to
reduce the amount of copy-paste but I think I should do that in a separate
exercise with broader scope. Thanks.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shukitchan/trafficserver multi-value-header
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/697.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #697
----
commit 19cd6a1feb214d9b076947e44e51788671d500d9
Author: Kit Chan <[email protected]>
Date: 2016-06-07T01:21:48Z
support multiple header with same name
----
> ts_lua plugin - support multiple headers with the same name
> -----------------------------------------------------------
>
> Key: TS-4510
> URL: https://issues.apache.org/jira/browse/TS-4510
> Project: Traffic Server
> Issue Type: Improvement
> Components: Lua, Plugins
> Reporter: Kit Chan
> Assignee: Kit Chan
> Fix For: 7.0.0
>
>
> Currently ts_lua plugin does not handle well when the request or response
> contains multiple header with the same name.
> We either retrieve the last value of first value of these headers and when we
> set new value to the header, we only change the first one and leave the rest
> there still.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)