[
https://issues.apache.org/jira/browse/TS-4515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15437458#comment-15437458
]
Petar Penkov commented on TS-4515:
----------------------------------
I am thinking of two ways the incorporation can happen:
1) Variable Expansion:
All of the SSL session field values described in the SSL Headers Plugin are
added as substitutions. An example is client.certificate substituted by <%ccrt>
or something similar. This seems to be a very flexible option and
implementation should not be challenging. My gut tells me this can be tricky to
use though I have no reasons to support this. This will also cause two thirds
of the supported substitutions to be SSL-related.
2) Adding an ssl-header operator:
This will be very similar to set-header and will look like "ssl-header NAME
FIELD" i.e "ssl-header SSL-Client-NotBefore client.notbefore". It should be
straightforward when to use the ssl-header. The downside of this is that yet
another way to add a header will be added which will be similar to the existing
ones and will not be adding much.
As with sharing the implementation, after the incorporation has been finished,
the sslheaders plugin can be moved to examples because it is short, achieves a
simple task and serves as a good model in my opinion.
> header_rewrite: Incorporate functionality from sslheaders plugin
> ----------------------------------------------------------------
>
> Key: TS-4515
> URL: https://issues.apache.org/jira/browse/TS-4515
> Project: Traffic Server
> Issue Type: New Feature
> Components: Plugins
> Reporter: Leif Hedstrom
> Fix For: 7.0.0
>
>
> I think it'd be useful to have the functionality that sslheaders provides
> incorporated into the more generic header_rewrite plugin.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
