You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Manjesh Nilange (JIRA)" <ji...@apache.org> on 2011/07/13 20:45:00 UTC
[jira] [Created] (TS-876) forward map based on request receive port
forward map based on request receive port
-----------------------------------------
Key: TS-876
URL: https://issues.apache.org/jira/browse/TS-876
Project: Traffic Server
Issue Type: New Feature
Components: Remap API
Reporter: Manjesh Nilange
Currently the port in the "from" fields of all remap rules are compared against the port in the request (explicitly in the request or implicitly deduced from the protocol). TS supports listening on multiple ports, so there is a use case for a remap rule that uses the TS port at which the request is received instead of the "request port".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TS-876) forward map based on request receive
port
Posted by "Igor Galić (Assigned JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Galić reassigned TS-876:
-----------------------------
Assignee: Igor Galić (was: Brian Geffon)
> forward map based on request receive port
> -----------------------------------------
>
> Key: TS-876
> URL: https://issues.apache.org/jira/browse/TS-876
> Project: Traffic Server
> Issue Type: New Feature
> Components: Remap API
> Reporter: Manjesh Nilange
> Assignee: Igor Galić
> Fix For: 3.1.0
>
> Attachments: TS876.fixed.patch, map_with_recv_port.patch
>
>
> Currently the port in the "from" fields of all remap rules are compared against the port in the request (explicitly in the request or implicitly deduced from the protocol). TS supports listening on multiple ports, so there is a use case for a remap rule that uses the TS port at which the request is received instead of the "request port".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-876) forward map based on request receive port
Posted by "Manjesh Nilange (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manjesh Nilange updated TS-876:
-------------------------------
Attachment: map_with_recv_port-trunk.patch
> forward map based on request receive port
> -----------------------------------------
>
> Key: TS-876
> URL: https://issues.apache.org/jira/browse/TS-876
> Project: Traffic Server
> Issue Type: New Feature
> Components: Remap API
> Reporter: Manjesh Nilange
> Assignee: Leif Hedstrom
> Fix For: 3.1.1
>
> Attachments: map_with_recv_port-trunk.patch, map_with_recv_port.patch, map_with_recv_port_v2.patch
>
>
> Currently the port in the "from" fields of all remap rules are compared against the port in the request (explicitly in the request or implicitly deduced from the protocol). TS supports listening on multiple ports, so there is a use case for a remap rule that uses the TS port at which the request is received instead of the "request port".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-876) forward map based on request receive
port
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13073312#comment-13073312 ]
Leif Hedstrom commented on TS-876:
----------------------------------
Manjesh: Any chance you can make a patch for "trunk"? Your v2 patch has numerious FAILED patchsets that prevents easy testing and review.
> forward map based on request receive port
> -----------------------------------------
>
> Key: TS-876
> URL: https://issues.apache.org/jira/browse/TS-876
> Project: Traffic Server
> Issue Type: New Feature
> Components: Remap API
> Reporter: Manjesh Nilange
> Assignee: Leif Hedstrom
> Fix For: 3.1.0
>
> Attachments: map_with_recv_port.patch, map_with_recv_port_v2.patch
>
>
> Currently the port in the "from" fields of all remap rules are compared against the port in the request (explicitly in the request or implicitly deduced from the protocol). TS supports listening on multiple ports, so there is a use case for a remap rule that uses the TS port at which the request is received instead of the "request port".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TS-876) forward map based on request receive
port
Posted by "Leif Hedstrom (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom reassigned TS-876:
--------------------------------
Assignee: Brian Geffon (was: Leif Hedstrom)
> forward map based on request receive port
> -----------------------------------------
>
> Key: TS-876
> URL: https://issues.apache.org/jira/browse/TS-876
> Project: Traffic Server
> Issue Type: New Feature
> Components: Remap API
> Reporter: Manjesh Nilange
> Assignee: Brian Geffon
> Fix For: 3.1.0
>
> Attachments: map_with_recv_port.patch
>
>
> Currently the port in the "from" fields of all remap rules are compared against the port in the request (explicitly in the request or implicitly deduced from the protocol). TS supports listening on multiple ports, so there is a use case for a remap rule that uses the TS port at which the request is received instead of the "request port".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-876) forward map based on request receive port
Posted by "Manjesh Nilange (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manjesh Nilange updated TS-876:
-------------------------------
Attachment: (was: map_with_recv_port.patch)
> forward map based on request receive port
> -----------------------------------------
>
> Key: TS-876
> URL: https://issues.apache.org/jira/browse/TS-876
> Project: Traffic Server
> Issue Type: New Feature
> Components: Remap API
> Reporter: Manjesh Nilange
> Assignee: vijaya bhaskar mamidi
> Fix For: 3.1.0
>
>
> Currently the port in the "from" fields of all remap rules are compared against the port in the request (explicitly in the request or implicitly deduced from the protocol). TS supports listening on multiple ports, so there is a use case for a remap rule that uses the TS port at which the request is received instead of the "request port".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-876) forward map based on request receive
port
Posted by "Brian Geffon (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195253#comment-13195253 ]
Brian Geffon commented on TS-876:
---------------------------------
Ok, I've uploaded a new patch TS876.fixed.patch that merges the two different commits into a single patch. I'm going to re-add TS-876 to 3.0.x/STATUS for backport.
> forward map based on request receive port
> -----------------------------------------
>
> Key: TS-876
> URL: https://issues.apache.org/jira/browse/TS-876
> Project: Traffic Server
> Issue Type: New Feature
> Components: Remap API
> Reporter: Manjesh Nilange
> Assignee: Brian Geffon
> Fix For: 3.1.0
>
> Attachments: TS876.fixed.patch, map_with_recv_port.patch
>
>
> Currently the port in the "from" fields of all remap rules are compared against the port in the request (explicitly in the request or implicitly deduced from the protocol). TS supports listening on multiple ports, so there is a use case for a remap rule that uses the TS port at which the request is received instead of the "request port".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-876) forward map based on request receive port
Posted by "Manjesh Nilange (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manjesh Nilange updated TS-876:
-------------------------------
Attachment: map_with_recv_port.patch
This patch introduces a new forward map directive - 'map_with_recv_port'. The regex qualifier can be applied to this mapping as well.
> forward map based on request receive port
> -----------------------------------------
>
> Key: TS-876
> URL: https://issues.apache.org/jira/browse/TS-876
> Project: Traffic Server
> Issue Type: New Feature
> Components: Remap API
> Reporter: Manjesh Nilange
> Attachments: map_with_recv_port.patch
>
>
> Currently the port in the "from" fields of all remap rules are compared against the port in the request (explicitly in the request or implicitly deduced from the protocol). TS supports listening on multiple ports, so there is a use case for a remap rule that uses the TS port at which the request is received instead of the "request port".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-876) forward map based on request receive port
Posted by "Brian Geffon (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Geffon updated TS-876:
----------------------------
Backport to Version: 3.0.3
> forward map based on request receive port
> -----------------------------------------
>
> Key: TS-876
> URL: https://issues.apache.org/jira/browse/TS-876
> Project: Traffic Server
> Issue Type: New Feature
> Components: Remap API
> Reporter: Manjesh Nilange
> Assignee: Brian Geffon
> Fix For: 3.1.0
>
> Attachments: TS876.fixed.patch, map_with_recv_port.patch
>
>
> Currently the port in the "from" fields of all remap rules are compared against the port in the request (explicitly in the request or implicitly deduced from the protocol). TS supports listening on multiple ports, so there is a use case for a remap rule that uses the TS port at which the request is received instead of the "request port".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-876) forward map based on request receive port
Posted by "Brian Geffon (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Geffon updated TS-876:
----------------------------
Backport to Version: (was: 3.0.3)
> forward map based on request receive port
> -----------------------------------------
>
> Key: TS-876
> URL: https://issues.apache.org/jira/browse/TS-876
> Project: Traffic Server
> Issue Type: New Feature
> Components: Remap API
> Reporter: Manjesh Nilange
> Assignee: Brian Geffon
> Fix For: 3.1.0
>
> Attachments: map_with_recv_port.patch
>
>
> Currently the port in the "from" fields of all remap rules are compared against the port in the request (explicitly in the request or implicitly deduced from the protocol). TS supports listening on multiple ports, so there is a use case for a remap rule that uses the TS port at which the request is received instead of the "request port".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-876) forward map based on request receive
port
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064852#comment-13064852 ]
Leif Hedstrom commented on TS-876:
----------------------------------
That would explain the old filename (remap.config vs the new remap.config.default). You really ought to switch to at least 2.1.9, or preferably 3.0.0, there are several important fixes since 2.1.7.
And yeah, getting patches off trunk would be preferably.
> forward map based on request receive port
> -----------------------------------------
>
> Key: TS-876
> URL: https://issues.apache.org/jira/browse/TS-876
> Project: Traffic Server
> Issue Type: New Feature
> Components: Remap API
> Reporter: Manjesh Nilange
> Assignee: Leif Hedstrom
> Fix For: 3.1.0
>
> Attachments: map_with_recv_port.patch, map_with_recv_port_v2.patch
>
>
> Currently the port in the "from" fields of all remap rules are compared against the port in the request (explicitly in the request or implicitly deduced from the protocol). TS supports listening on multiple ports, so there is a use case for a remap rule that uses the TS port at which the request is received instead of the "request port".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-876) forward map based on request receive port
Posted by "Igor Galić (Updated JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Galić updated TS-876:
--------------------------
Backport to Version: (was: 3.0.3)
Fix Version/s: 3.0.3
> forward map based on request receive port
> -----------------------------------------
>
> Key: TS-876
> URL: https://issues.apache.org/jira/browse/TS-876
> Project: Traffic Server
> Issue Type: New Feature
> Components: Remap API
> Reporter: Manjesh Nilange
> Assignee: Igor Galić
> Fix For: 3.1.0, 3.0.3
>
> Attachments: TS876.fixed.patch, map_with_recv_port.patch
>
>
> Currently the port in the "from" fields of all remap rules are compared against the port in the request (explicitly in the request or implicitly deduced from the protocol). TS supports listening on multiple ports, so there is a use case for a remap rule that uses the TS port at which the request is received instead of the "request port".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-876) forward map based on request receive
port
Posted by "Manjesh Nilange (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079603#comment-13079603 ]
Manjesh Nilange commented on TS-876:
------------------------------------
This patch applies cleanly on 3.0.0 and trunk.
> forward map based on request receive port
> -----------------------------------------
>
> Key: TS-876
> URL: https://issues.apache.org/jira/browse/TS-876
> Project: Traffic Server
> Issue Type: New Feature
> Components: Remap API
> Reporter: Manjesh Nilange
> Assignee: Leif Hedstrom
> Fix For: 3.1.1
>
> Attachments: map_with_recv_port-trunk.patch, map_with_recv_port.patch, map_with_recv_port_v2.patch
>
>
> Currently the port in the "from" fields of all remap rules are compared against the port in the request (explicitly in the request or implicitly deduced from the protocol). TS supports listening on multiple ports, so there is a use case for a remap rule that uses the TS port at which the request is received instead of the "request port".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-876) forward map based on request receive port
Posted by "Manjesh Nilange (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manjesh Nilange updated TS-876:
-------------------------------
Attachment: (was: map_with_recv_port_v2.patch)
> forward map based on request receive port
> -----------------------------------------
>
> Key: TS-876
> URL: https://issues.apache.org/jira/browse/TS-876
> Project: Traffic Server
> Issue Type: New Feature
> Components: Remap API
> Reporter: Manjesh Nilange
> Assignee: vijaya bhaskar mamidi
> Fix For: 3.1.0
>
>
> Currently the port in the "from" fields of all remap rules are compared against the port in the request (explicitly in the request or implicitly deduced from the protocol). TS supports listening on multiple ports, so there is a use case for a remap rule that uses the TS port at which the request is received instead of the "request port".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-876) forward map based on request receive port
Posted by "Manjesh Nilange (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manjesh Nilange updated TS-876:
-------------------------------
Attachment: (was: map_with_recv_port-trunk.patch)
> forward map based on request receive port
> -----------------------------------------
>
> Key: TS-876
> URL: https://issues.apache.org/jira/browse/TS-876
> Project: Traffic Server
> Issue Type: New Feature
> Components: Remap API
> Reporter: Manjesh Nilange
> Assignee: vijaya bhaskar mamidi
> Fix For: 3.1.0
>
>
> Currently the port in the "from" fields of all remap rules are compared against the port in the request (explicitly in the request or implicitly deduced from the protocol). TS supports listening on multiple ports, so there is a use case for a remap rule that uses the TS port at which the request is received instead of the "request port".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-876) forward map based on request receive port
Posted by "Manjesh Nilange (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manjesh Nilange updated TS-876:
-------------------------------
Attachment: map_with_recv_port_v2.patch
Modified patch. The old patch was not handling the case when the only forward mappings were of the 'map_with_recv_port' type. It was segfaulting.
> forward map based on request receive port
> -----------------------------------------
>
> Key: TS-876
> URL: https://issues.apache.org/jira/browse/TS-876
> Project: Traffic Server
> Issue Type: New Feature
> Components: Remap API
> Reporter: Manjesh Nilange
> Assignee: Leif Hedstrom
> Fix For: 3.1.0
>
> Attachments: map_with_recv_port.patch, map_with_recv_port_v2.patch
>
>
> Currently the port in the "from" fields of all remap rules are compared against the port in the request (explicitly in the request or implicitly deduced from the protocol). TS supports listening on multiple ports, so there is a use case for a remap rule that uses the TS port at which the request is received instead of the "request port".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-876) forward map based on request receive port
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-876:
-----------------------------
Fix Version/s: 3.1.0
Assignee: Leif Hedstrom
> forward map based on request receive port
> -----------------------------------------
>
> Key: TS-876
> URL: https://issues.apache.org/jira/browse/TS-876
> Project: Traffic Server
> Issue Type: New Feature
> Components: Remap API
> Reporter: Manjesh Nilange
> Assignee: Leif Hedstrom
> Fix For: 3.1.0
>
> Attachments: map_with_recv_port.patch
>
>
> Currently the port in the "from" fields of all remap rules are compared against the port in the request (explicitly in the request or implicitly deduced from the protocol). TS supports listening on multiple ports, so there is a use case for a remap rule that uses the TS port at which the request is received instead of the "request port".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-876) forward map based on request receive
port
Posted by "Manjesh Nilange (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064851#comment-13064851 ]
Manjesh Nilange commented on TS-876:
------------------------------------
Oh, I forgot to mention that I'm working off 2.1.7. This is what we are using. So whether the patch applies cleanly to other branches has to be verified, though I think it more or less will.
When I get to working off trunk (I assume that is what you guys are doing), I'll update this ticket with a verified patch.
> forward map based on request receive port
> -----------------------------------------
>
> Key: TS-876
> URL: https://issues.apache.org/jira/browse/TS-876
> Project: Traffic Server
> Issue Type: New Feature
> Components: Remap API
> Reporter: Manjesh Nilange
> Assignee: Leif Hedstrom
> Fix For: 3.1.0
>
> Attachments: map_with_recv_port.patch, map_with_recv_port_v2.patch
>
>
> Currently the port in the "from" fields of all remap rules are compared against the port in the request (explicitly in the request or implicitly deduced from the protocol). TS supports listening on multiple ports, so there is a use case for a remap rule that uses the TS port at which the request is received instead of the "request port".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-876) forward map based on request receive port
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-876:
-----------------------------
Fix Version/s: (was: 3.1.0)
3.1.1
Moving this out to 3.1.1, waiting for an easier to land patch. Please move it back if you think it'll get landed in the next week or so.
> forward map based on request receive port
> -----------------------------------------
>
> Key: TS-876
> URL: https://issues.apache.org/jira/browse/TS-876
> Project: Traffic Server
> Issue Type: New Feature
> Components: Remap API
> Reporter: Manjesh Nilange
> Assignee: Leif Hedstrom
> Fix For: 3.1.1
>
> Attachments: map_with_recv_port.patch, map_with_recv_port_v2.patch
>
>
> Currently the port in the "from" fields of all remap rules are compared against the port in the request (explicitly in the request or implicitly deduced from the protocol). TS supports listening on multiple ports, so there is a use case for a remap rule that uses the TS port at which the request is received instead of the "request port".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-876) forward map based on request receive port
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-876:
-----------------------------
Fix Version/s: (was: 3.1.1)
3.1.0
Assignee: vijaya bhaskar mamidi (was: Leif Hedstrom)
> forward map based on request receive port
> -----------------------------------------
>
> Key: TS-876
> URL: https://issues.apache.org/jira/browse/TS-876
> Project: Traffic Server
> Issue Type: New Feature
> Components: Remap API
> Reporter: Manjesh Nilange
> Assignee: vijaya bhaskar mamidi
> Fix For: 3.1.0
>
> Attachments: map_with_recv_port-trunk.patch, map_with_recv_port.patch, map_with_recv_port_v2.patch
>
>
> Currently the port in the "from" fields of all remap rules are compared against the port in the request (explicitly in the request or implicitly deduced from the protocol). TS supports listening on multiple ports, so there is a use case for a remap rule that uses the TS port at which the request is received instead of the "request port".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-876) forward map based on request receive port
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-876:
-----------------------------
Backport to Version: 3.0.2
> forward map based on request receive port
> -----------------------------------------
>
> Key: TS-876
> URL: https://issues.apache.org/jira/browse/TS-876
> Project: Traffic Server
> Issue Type: New Feature
> Components: Remap API
> Reporter: Manjesh Nilange
> Assignee: vijaya bhaskar mamidi
> Fix For: 3.1.0
>
> Attachments: map_with_recv_port.patch
>
>
> Currently the port in the "from" fields of all remap rules are compared against the port in the request (explicitly in the request or implicitly deduced from the protocol). TS supports listening on multiple ports, so there is a use case for a remap rule that uses the TS port at which the request is received instead of the "request port".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TS-876) forward map based on request receive
port
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064824#comment-13064824 ]
Leif Hedstrom commented on TS-876:
----------------------------------
Quick nit-picky comment: remap.config is not the "source" file, they were all renamed to .default, e.g. remap.config.default. Would you mind producing a patch with that fixed, just for clarity?
> forward map based on request receive port
> -----------------------------------------
>
> Key: TS-876
> URL: https://issues.apache.org/jira/browse/TS-876
> Project: Traffic Server
> Issue Type: New Feature
> Components: Remap API
> Reporter: Manjesh Nilange
> Assignee: Leif Hedstrom
> Fix For: 3.1.0
>
> Attachments: map_with_recv_port.patch
>
>
> Currently the port in the "from" fields of all remap rules are compared against the port in the request (explicitly in the request or implicitly deduced from the protocol). TS supports listening on multiple ports, so there is a use case for a remap rule that uses the TS port at which the request is received instead of the "request port".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (TS-876) forward map based on request receive
port
Posted by "Brian Geffon (Reopened) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Geffon reopened TS-876:
-----------------------------
Backport to Version: 3.0.3
Assignee: Leif Hedstrom (was: vijaya bhaskar mamidi)
This applies cleanly to 3.0.2 for me and should be considered for 3.0.3
> forward map based on request receive port
> -----------------------------------------
>
> Key: TS-876
> URL: https://issues.apache.org/jira/browse/TS-876
> Project: Traffic Server
> Issue Type: New Feature
> Components: Remap API
> Reporter: Manjesh Nilange
> Assignee: Leif Hedstrom
> Fix For: 3.1.0
>
> Attachments: map_with_recv_port.patch
>
>
> Currently the port in the "from" fields of all remap rules are compared against the port in the request (explicitly in the request or implicitly deduced from the protocol). TS supports listening on multiple ports, so there is a use case for a remap rule that uses the TS port at which the request is received instead of the "request port".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-876) forward map based on request receive port
Posted by "Manjesh Nilange (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manjesh Nilange updated TS-876:
-------------------------------
Attachment: map_with_recv_port.patch
> forward map based on request receive port
> -----------------------------------------
>
> Key: TS-876
> URL: https://issues.apache.org/jira/browse/TS-876
> Project: Traffic Server
> Issue Type: New Feature
> Components: Remap API
> Reporter: Manjesh Nilange
> Assignee: vijaya bhaskar mamidi
> Fix For: 3.1.0
>
> Attachments: map_with_recv_port.patch
>
>
> Currently the port in the "from" fields of all remap rules are compared against the port in the request (explicitly in the request or implicitly deduced from the protocol). TS supports listening on multiple ports, so there is a use case for a remap rule that uses the TS port at which the request is received instead of the "request port".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-876) forward map based on request receive port
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-876:
-----------------------------
Backport to Version: (was: 3.0.2)
> forward map based on request receive port
> -----------------------------------------
>
> Key: TS-876
> URL: https://issues.apache.org/jira/browse/TS-876
> Project: Traffic Server
> Issue Type: New Feature
> Components: Remap API
> Reporter: Manjesh Nilange
> Assignee: vijaya bhaskar mamidi
> Fix For: 3.1.0
>
> Attachments: map_with_recv_port.patch
>
>
> Currently the port in the "from" fields of all remap rules are compared against the port in the request (explicitly in the request or implicitly deduced from the protocol). TS supports listening on multiple ports, so there is a use case for a remap rule that uses the TS port at which the request is received instead of the "request port".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TS-876) forward map based on request receive
port
Posted by "Igor Galić (Resolved JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Galić resolved TS-876.
---------------------------
Resolution: Fixed
Commit: cefaa40711986d24f3a2b7030d046b22b61f2ece
> forward map based on request receive port
> -----------------------------------------
>
> Key: TS-876
> URL: https://issues.apache.org/jira/browse/TS-876
> Project: Traffic Server
> Issue Type: New Feature
> Components: Remap API
> Reporter: Manjesh Nilange
> Assignee: Igor Galić
> Fix For: 3.0.3, 3.1.0
>
> Attachments: TS876.fixed.patch, map_with_recv_port.patch
>
>
> Currently the port in the "from" fields of all remap rules are compared against the port in the request (explicitly in the request or implicitly deduced from the protocol). TS supports listening on multiple ports, so there is a use case for a remap rule that uses the TS port at which the request is received instead of the "request port".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-876) forward map based on request receive port
Posted by "Brian Geffon (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Geffon updated TS-876:
----------------------------
Attachment: TS876.fixed.patch
> forward map based on request receive port
> -----------------------------------------
>
> Key: TS-876
> URL: https://issues.apache.org/jira/browse/TS-876
> Project: Traffic Server
> Issue Type: New Feature
> Components: Remap API
> Reporter: Manjesh Nilange
> Assignee: Brian Geffon
> Fix For: 3.1.0
>
> Attachments: TS876.fixed.patch, map_with_recv_port.patch
>
>
> Currently the port in the "from" fields of all remap rules are compared against the port in the request (explicitly in the request or implicitly deduced from the protocol). TS supports listening on multiple ports, so there is a use case for a remap rule that uses the TS port at which the request is received instead of the "request port".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira