[
https://issues.apache.org/jira/browse/TS-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-81:
----------------------------
Description:
Currently, remap rules are stored in different structures and looked up
separately based on type (forward, reverse, etc.). It'd be better design and
more maintainable to process (store, search) all rules in one structure and
then use type to determine action.
A fundamental problem with our current implementation is that the order in
remap.config is not honored. E.g. a map directive always takes precedence over
any redirect directives (if both matches).
was:
Currently, remap rules are stored in different structures and looked up
separately based on type (forward, reverse, etc.). It'd be better design and
more maintainable to process (store, search) all rules in one structure and
then use type to determine action.
> Have one single place to store and lookup remap rules irrespective of type
> --------------------------------------------------------------------------
>
> Key: TS-81
> URL: https://issues.apache.org/jira/browse/TS-81
> Project: Traffic Server
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.0.0a
> Reporter: Manjesh Nilange
> Priority: Minor
> Labels: A
> Fix For: 6.0.0
>
>
> Currently, remap rules are stored in different structures and looked up
> separately based on type (forward, reverse, etc.). It'd be better design and
> more maintainable to process (store, search) all rules in one structure and
> then use type to determine action.
> A fundamental problem with our current implementation is that the order in
> remap.config is not honored. E.g. a map directive always takes precedence
> over any redirect directives (if both matches).
--
This message was sent by Atlassian JIRA
(v6.1#6144)
