[
https://issues.apache.org/jira/browse/TS-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718147#comment-13718147
]
Aidan McGurn commented on TS-2060:
----------------------------------
thanks for the comments...
its general usefulness then is up for debate -
but one thing for sure is we found it confusing as to why there was a
limitation of one ipv4 address to bind to and why decoupled from the port
information... that was without knowing this could be achieved using a
different parameter, ip-in.
Maybe as a minimum records.config could expand the comments to say
incoming_ip_to_bind is mean;t as global scope parameter which will apply to all
ports in http_server_ports - to override this at individual port scope, use
ip-in in http_server_ports (at least i assume this is the precedence).
> 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
