[
https://issues.apache.org/jira/browse/TS-4500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15336263#comment-15336263
]
ASF GitHub Bot commented on TS-4500:
------------------------------------
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/692
Hmmm. Well, update-cookie is similarly confusing, in that the name implies
that it'd only work if the cookie already exists (at least to me :). Damned if
we do, damned if we don't ... set-cookie would be inline with what other
existing operators do, but I agree that there is the potential for confusion on
Set-Cookie. @bgaff make a decision! :-)
> add cookie-rewrite functionality into header-rewrite plugin
> -----------------------------------------------------------
>
> Key: TS-4500
> URL: https://issues.apache.org/jira/browse/TS-4500
> Project: Traffic Server
> Issue Type: New Feature
> Components: Plugins
> Reporter: Zhang Zizhong
> Assignee: Zhang Zizhong
> Fix For: 7.0.0
>
>
> add cookie-rewrite functionality into header-rewrite plugin.
> There're three cookie handling operators added, including *add-cookie*,
> *rm-cookie* and *update-cookie*.
> *add-cookie* adds a key-value pair into Cookie. If the given key is already
> in Cookie, do nothing.
> *rm-cookie* remove a pair with the given key from Cookie.
> *update-cookie* sets the value with the given key to the given value. If the
> given key doesn't exist, add a new pair into Cookie. So the only difference
> between *add-cookie* and *update-cookie* is overwriting an existing pair or
> not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
