unexpected api endpoint availability

[teodorescuserban]

I am using souin as caddy module.

I only cache some of the requests. I was very surprised to notice (after a couple of hours of unsuccessful tries) that in certain configurations the souin api endpoint is not available. More precise, if a request to /souin-api/souin is not configured to be cached, the api won't respond.

Like in this Caddyfile example:

{
    cache
}

:80 {

    @somecache path /i-cache-this
    @nocache not path /i-cache-this

    route @somecache {
        cache
        respond "caching."
    }

    route @nocache {
        respond "not caching. and no souin api."    
    }
}

Now, I don't have a sane suggestion. My first instinct would tell me that it would be nice to have the souin-api endpoint liked to the caddy admin port instead. But there are a number of problems with that.

Perhaps the best solution would br to just document that (with a nice example of how to also secure the souin api endpoint from external).

Keep up the good work, @darkweak !

[darkweak]

Hey @teodorescuserban I plan to bring this feature in the PR #589.