-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Allow temporary disable of a proxy using checkbox #8
New issue
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
Comments
And what should a user see in their browser when a host is disabled? The default landing page, which is a http 200, or should they get a 404 not found? |
Perhaps a default nginx 404. Or the screen you get when the proxies IP is not available.
|
+1 to this, when disabled I think the user should see default page when no matching hostname. (same behavior as if you delete it, but without deleting of course haha) Thanks! |
I'd like to up vote this one as well. Although I would opt for a global configuration setting that would let you choose what response code to return when a site is disabled - Not Found, Service Unavailable etc... Just to add to this though - Having the toggle either in the modal or the menu as well as having the "Enabled" status shown on the table list as well, and the dashboard to show the total hosts with an additional number of disabled hosts (if any) |
Added in v2.0.8. |
As the title says, a proxy or redirect should be able to be disabled using a checkbox on the edit modal.
The text was updated successfully, but these errors were encountered: