You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I really liked Caddy v1 basicauth and would like to see this feature in Caddy v2, too.
For little private projects or testing purposes, quickly "securing" them via basicauth is convenient and I used it a lot in Caddyfile v1.
If possible keeping the simple syntax just like in Caddy v2 would be awesome.
2. Why is this feature a useful, necessary, and/or important addition to this project?
Restrict access to specific webfolders quickly and convenient just like in Caddy v1.
3. What alternatives are there, or what are you doing in the meantime to work around the lack of this feature?
In the meantime, I run a second instance of Caddy which binds to localhost on a different port to work on some projects in private, but having them online in one instance allows for specific people to access the files if necessary to test, etc.
4. Please link to any relevant issues, pull requests, or other discussions.
I've actually got this mostly working locally, but I need to figure out how to design the more general authentication module before I'm ready to commit basic auth (which is just one form of authentication).
Hm, I can probably get this out next week, but the design may change in a breaking way before the final version. Just be aware of that.
This implements HTTP basicauth into Caddy 2. The basic auth module will
not work with passwords that are not securely hashed, so a subcommand
hash-password was added to make it convenient to produce those hashes.
Also included is Caddyfile support.
Closes#2747.
1. What would you like to have changed?
I really liked Caddy v1 basicauth and would like to see this feature in Caddy v2, too.
For little private projects or testing purposes, quickly "securing" them via basicauth is convenient and I used it a lot in Caddyfile v1.
If possible keeping the simple syntax just like in Caddy v2 would be awesome.
2. Why is this feature a useful, necessary, and/or important addition to this project?
Restrict access to specific webfolders quickly and convenient just like in Caddy v1.
3. What alternatives are there, or what are you doing in the meantime to work around the lack of this feature?
In the meantime, I run a second instance of Caddy which binds to localhost on a different port to work on some projects in private, but having them online in one instance allows for specific people to access the files if necessary to test, etc.
4. Please link to any relevant issues, pull requests, or other discussions.
https://caddy.community/t/v2-basicauth-feature/
The text was updated successfully, but these errors were encountered: