Route Priority Misconfiguration Hijacking
warningOverly broad route regex patterns (like catching any path starting with 'p') can hijack requests intended for other routes. Kong processes routes in priority order, so catch-all patterns must be carefully ordered to avoid stealing traffic.
Use Kong-Debug: 1 header to inspect which route and service handled a request. If requests unexpectedly match wrong routes, or if high-priority routes never receive traffic, check route regex patterns and priority ordering. Monitor route match distribution for unexpected imbalances.
Review route path patterns for overlapping regex. Use Kong Manager or API to list routes sorted by priority. Ensure specific routes have higher priority than catch-all patterns. Test with Kong-Debug header to verify routing behavior matches intent. Avoid broad patterns like /p* in production without explicit priority management.