We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Would you recommend using this in production mode?
If you do so, are you planning to implement some kind of access control anytime soon?
The text was updated successfully, but these errors were encountered:
I don't recommend using Rin in a production environment for several reasons.
However, I know some developers need to protect a development environment too. So, I planned to implement access control in the future.
At the moment, if you want to restrict access to Rin inspector, you can implement a workaround in the middleware pipeline.
var options = app.ApplicationServices.GetService<RinOptions>(); app.MapWhen( ctx => ctx.Request.Path.StartsWithSegments(options.Inspector.MountPath) && /* ctx.Request ...some conditions ... */, app2 => { app2.Use((ctx, next) => { ctx.Response.StatusCode = 403; ctx.Response.WriteAsync("Forbidden"); return Task.CompletedTask; }); }); app.UseRin(); ...
Sorry, something went wrong.
No branches or pull requests
Would you recommend using this in production mode?
If you do so, are you planning to implement some kind of access control anytime soon?
The text was updated successfully, but these errors were encountered: