Hi! Is it possible to add path based authorisation to files served with

static { ... }

? What I would like to do: • user A can access files from

./a

folder • user B can access files from

./a

and

./b

folders Authentication is done in a very different part of the application. I wouldn't touch that if there is a way. Actually, I shouldn't touch that as authentication and authorisation are two different topics. As I see, my only option right now is to write (i.e. cut&paste from Ktor) my own handling of static resources and add the authorisation. Are there any better options? Thanks in advance.

I guess you could work with an interceptor using different paths?

routing {
    route("/assets") {
        static {
            files("./a")
        }
        route("/protected") {
              intercept(ApplicationCallPipeline.Call) {
                    if (!call.user.isAllowedToAccessProtectedResources) return@intercept call.respond(HttpStatusCode.Forbidden)
                    proceed()
              }
              static {
                  files("./b")
              }
        }
    }
}

Good point, thank you. I had some fuzzy memory about having interceptors but a short look a the documentation did not reveal the details. Thanks for the example, I'll give it a try.

That sounds like you need some kind of context.