[TS-81] Have one single place to store and lookup remap rules irrespective of type

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 2.0.0a
• Fix Version/s: 8.0.0
• Component/s: Core, HTTP
• Labels: incompatible
• Assignee: Unassigned
• Reporter: Manjesh Nilange
• Created: 10/Dec/09 00:25
• Updated: 15/Aug/16 15:46

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).

Issue Links

• duplicates: TS-2142 redirects placed before maps don't happen because of precedence, this confuses users
• duplicates: TS-2313 redirect with map
• is related to: TS-481 Poorly handled remap with proxy.config.url_remap.url_remap_mode set to 2
• is related to: TS-1984 Allow for somewhat more flexible wildcards in remap.config