[
https://issues.apache.org/jira/browse/TS-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14223946#comment-14223946
]
Phil Sorber commented on TS-3108:
---------------------------------
Looking at other usage "SERVER" usually refers to the origin server. That's not
what this is at all. It's probably closer to "CLIENT-PORT" but that suggests
the port of the remote end of the client connection, what this is also not. It
seems like the best name would be something like "INCOMING-CLIENT-PORT" or
"CLIENT-INCOMING-PORT" but that is awful wordy and it's unclear that anyone
would care about the remote client port, so that "INCOMING-PORT" seems to be
sufficient. I hope that explanation is compelling enough. I will close this
ticket unless there is further disagreement.
We can open a separate issue to implement "OUTGOING-PORT" (which would be
remote server port) so that 5.2.0 can proceed.
> Add port matching condition to header_rewrite
> ---------------------------------------------
>
> Key: TS-3108
> URL: https://issues.apache.org/jira/browse/TS-3108
> Project: Traffic Server
> Issue Type: New Feature
> Reporter: Phil Sorber
> Assignee: Phil Sorber
> Priority: Critical
> Fix For: 5.2.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
