What is the significance of rule ORDER inside authorizeHttpRequests()?

Spring Security evaluates requestMatchers rules in the order they are declared and applies the FIRST one that matches a given request path — subsequent, even more specific, rules are never reached if an earlier broader rule already matched. This is why specific patterns (like /api/admin/**) must be declared before broader catch-all patterns (like /api/**).