Route Level security

Was thinking of something like this.

Thoughts?

this.Get("/", async ctx => await this.RequiresAuthentication(async innerctx => await innerctx.WriteAsync("authed")));

[RagingKore]

that looks more atractive and doable. I would go with full pipeline composition as an alternative.

Here are some examples:

public class PlayersModule : CarterModule {
  public PlayersModule() {
    Route("/players/{:id}")
      .Authorize()
      .Get(ctx => // do something authorized );
 
    Route("/players/{:id}")
      .AuthorizeWithClaims(x => x.Type == "Admin")
      .Post(ctx => // do something authorized );
      
    Route("/players/{:id}")
      .Anonymous()
      .Put(ctx => // do something);
      
    Route("/players/{:id}")
      .Pipe(ctx => // do whatever my heart desires)
      .Delete(ctx => // do something authorized );
  }
}

[JoeStead]

It will require some sort of Carter pipeline intertwined with the ASP.NET one (I don’t think the details of which need to be exposed), so will require a bit more upfront thought, but it avoids specific CarterRequest and CarterResponse objects, whilst taking the extensibility up to 11.