`log_skip` + `abort` doesn't abort request when outside `handle` block

[Kangaroux]

Issue Details

Use case: trying to block spam requests and also not log them

@naughtyUserAgents {
    # Literally just spams favicon.ico. Not related with DuckDuckGo
    header User-Agent *ddg_win*
}

log_skip @naughtyUserAgents
abort @naughtyUserAgents

This doesn't work as I expected: it skips the log but allows the request through.

Wrapping it with a handle does work correctly:

handle @naughtyUserAgents {
    log_skip
    abort
}

Interestingly, this works:

handle_errors {
    log_skip @matcher
    abort @matcher
}

Assistance Disclosure

AI not used

If AI was used, describe the extent to which it was used.

No response

[steadytao]

route seems like it would be the right workaround for now:

route @naughtyUserAgents {
    log_skip
    abort
}

But I still think this is a small bug. log_skip @naughtyUserAgents + abort @naughtyUserAgents at the top level should work especially since the same logic works once wrapped in handle.

[francislavoie]

I don't see why that wouldn't work. What else is in your config? The whole thing matters.

Adapt your config to JSON, you'll see the "real" order that directives run, since the Caddyfile sorts directives.