Is your feature request related to a problem? Please describe.
By design there is no mapping between one route and set of modules. Thus all routes' traffic might go throught all modules. To avoid this each kind of module have to design a way to skip part of traffic.
The design has serveral disadvantage:
- It's harder to figure out a http request goes through which modules.
- A wrong matcher could result all traffic run through a not very good performance module, causing cluster level traffic jam.
- Different module might have different way to config how to skip certain route / url path, making config harder to be right.
Describe the solution you'd like
Allow to config modules by route, each route may map to a sequence of modules. HandleAccept, HandleHandshake still use global modules.
Describe alternatives you've considered
None.
Additional context
None
Is your feature request related to a problem? Please describe.
By design there is no mapping between one route and set of modules. Thus all routes' traffic might go throught all modules. To avoid this each kind of module have to design a way to skip part of traffic.
The design has serveral disadvantage:
Describe the solution you'd like
Allow to config modules by route, each route may map to a sequence of modules. HandleAccept, HandleHandshake still use global modules.
Describe alternatives you've considered
None.
Additional context
None