[
https://issues.apache.org/jira/browse/TS-4340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15280765#comment-15280765
]
Brian Geffon edited comment on TS-4340 at 5/11/16 8:33 PM:
-----------------------------------------------------------
~~ [~psudaemon] this was tagged as fixed in 6.2 but it doesn't appear to have
landed before 6.2 was branched, can we please backport.~~
Disregard
was (Author: briang):
[~psudaemon] this was tagged as fixed in 6.2 but it doesn't appear to have
landed before 6.2 was branched, can we please backport.
> `proxy.config.http.origin_max_connections` only matches on IP
> -------------------------------------------------------------
>
> Key: TS-4340
> URL: https://issues.apache.org/jira/browse/TS-4340
> Project: Traffic Server
> Issue Type: Bug
> Reporter: Thomas Jackson
> Assignee: Brian Geffon
> Fix For: 6.2.0
>
>
> As of today if you set a maximum number of connections to an origin (using
> `proxy.config.http.origin_max_connections`) the connections for an origin are
> counted by only checking the IP of connection (not a combination of schema,
> port, and IP). From conversations on IRC it seems like checking with
> `http://trafficserver.readthedocs.org/en/5.3.x/reference/configuration/records.config.en.html#proxy-config-http-server-session-sharing-match`
> to determine what matches will work.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
