Skip to content
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

Add support for .htaccess/htpasswd #63

Closed
jamo opened this issue Dec 22, 2016 · 4 comments
Closed

Add support for .htaccess/htpasswd #63

jamo opened this issue Dec 22, 2016 · 4 comments

Comments

@jamo
Copy link

jamo commented Dec 22, 2016

There has been cases where the single username+password for http basic auth just isn't enough.

So we should consider adding a full .htaccess/.htpasswd basic auth support to easily allow configuring multiple users with individual passwords.

@derhuerst
Copy link

[imho]

I think in the year of 2017, we don't need .htpasswd. Often, users store (hashed) passwords in the webroot. Authentication should nowadays be done by either by a (reverse) proxy or a separate auth service. Theoretically, even password authentication should be a thing of the past.

For the simple use case of setting up and adhoc web server, user & pw auth is sufficient.

I guess this is an ideological decision wether supporting these use cases is worth it for zeit and the broader community.

@jamo
Copy link
Author

jamo commented Dec 22, 2016

Yeah, necessary .htpasswd isn't the auth file format we should have.
But it should be something that wouldn't vendor lock and that is hassle free.

@derhuerst
Copy link

Not sure I expressed clearly enough what my opinion on this matter is. If I did, don't take this as an offence.

I think it's not the job of serve to deal with any auth more sophisticated than user/pw. It should be done by another service (as in web service) or proxy/api layer.

I've been following the development of http-server for a while. This is a feature that, as you can see with many feature requests over at http-server, only serves the needs of a very narrow user base and can easily be done by external packages.

@leo
Copy link
Contributor

leo commented Jan 12, 2017

I agree with both of you. But overall, I think this would be too much for this little package. People should put something on top and use another service.

@leo leo closed this as completed Jan 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants