SpringCloud in Gateway Routing matching problem

SpringCloud Gateway Routing match in order

When using gateway routing done, the request has been 404. In the service name address, routing keys match the correct situation is always 404.

The brothers do not want to waste time looking directly your conclusion

in conclusion:

This match is the route in accordance with the order of one to one matched
do not have to match in two key routes while serving, otherwise may be intercepted over the service.

The following figure. Access to consumer / 8 have the correct routing can match, but always reported 404. So it might be above suspicion / to intercept. **
Here Insert Picture Description

So it did the following test can be found, matching routing key from the top down, not according to the level of matching.
Here Insert Picture Description

Published 31 original articles · won praise 8 · views 1502

Guess you like

Origin blog.csdn.net/qq_37126480/article/details/104685299