[
https://issues.apache.org/jira/browse/TS-4500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15334450#comment-15334450
]
ASF GitHub Bot commented on TS-4500:
------------------------------------
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/692
Looks good. One more thing, didn't think about it last time: The
update-cookie, will that work if the cookie doesn't already exist? If so, can
we call it set-cookie instead? This is in line with our existing set-header /
add-header operators. update-cookie sounds like it'd only work if the cookie
value already exist, which seems harder to use than just a set-cookie which
will overwrite any existing value for the cookie (whereas add-cookie should add
it regardless I think?).
> 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)
