[
https://issues.apache.org/jira/browse/TS-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13717862#comment-13717862
]
Leif Hedstrom commented on TS-2060:
-----------------------------------
I don't think documentation is a solution to confusing configuration. Most
people will only read a small fraction of the docs, if any :)
I don't care strongly here, but I think one configuration flexible to hold most
common configs with little overhead would be preferable.
That said, I moved it out for now.
-- Leif
> proxy.local.incoming_ip_to_bind is superfluous
> ----------------------------------------------
>
> Key: TS-2060
> URL: https://issues.apache.org/jira/browse/TS-2060
> Project: Traffic Server
> Issue Type: Improvement
> Components: Core
> Reporter: Aidan McGurn
> Fix For: 3.5.1
>
>
> Why do ATS bother with this parameter?:
> LOCAL proxy.local.incoming_ip_to_bind STRING 10.20.41.15
> Which is limited to 2 IP’s and is not associated with the port information -
> This can all be achieved with:
> CONFIG proxy.config.http.server_ports STRING
> 3128:ipv4:tr-full:ip-in=10.20.41.15 3128:ipv4:tr-full:ip-in=10.20.50.27
> and with better granularity where we can assign individual ports to ip’s and
> not limited to 2.
> maybe this has already been taken out of ATS but if not why not?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
