Unautheticated resources, determined by patterns, should be distinguished by the http method.

When I was using this in my project, I came across the problem where I was patching, deleting and getting a resource that shared the same pattern in the routes config.

Whilst I want the patch and delete operations to be authenticated, I want the get operation to be unauthenticated. Because of this, if I register the GET as unauthenticated, I was experiencing the unwanted behaviour that other operations were open too.