You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Alan M. Carroll (JIRA)" <ji...@apache.org> on 2013/11/06 21:43:17 UTC

[jira] [Commented] (TS-2060) proxy.local.incoming_ip_to_bind is superfluous

    [ https://issues.apache.org/jira/browse/TS-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815274#comment-13815274 ] 

Alan M. Carroll commented on TS-2060:
-------------------------------------

I have updated the documentation as suggested and will therefore close this bug.

> 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
>            Assignee: Alan M. Carroll
>             Fix For: 4.1.0
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)