-
Notifications
You must be signed in to change notification settings - Fork 694
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
Option for enabling HTTPS #178
Comments
It's recommended to add nginx proxy or similar as SSL termination, it's not performant enough in node. |
+1 for this request. For me Maybe it's out of scope or more work than the devs want to do, but I think "it would be slower than nginx" isn't an argument against adding TLS/HTTPS to this tool. |
@DanielBaird did you ever find something that would do SSL like |
@mrmartineau Best so far is Caddy ( https://caddyserver.com ), where something like
...will start serving the current dir at myproject.com via http and https using a cert from letsencrypt. |
@mrmartineau Do you need ssl just for |
@DanielBaird thanks for the tip, I will give it a try. @albinekb yes. Both, I've been using |
I'm happy to accept a PR for this! |
maybe a collaboration /merge would be great between the two of you guys. https://github.com/indexzero/http-server |
I've a semi-working branch for this and I'll try to submit a PR as soon as I sand off some of the rough edges. 🙂 |
* Support HTTPS This should hopefully resolve #178. It uses the example given in the `micro` examples of `with-https`. It has some rough edges still that needed to be sanded down: * Choosing a specific short flag name for ssl (and if the initial flag should still be called ssl; I'm tempted to rename it to `https` or what have you). * The example always acks with 200 and the example object. * It does not support compression and merely overwrites the previous server var. * Pass appropriate handler to https server This also calls `compress' on the handler when the `unzipped' flag is not present. * Move https import to appropriate section * Change SSL flag copy * Merge in master to update package-lock.json * Address conflicts * Use master package-lock.json to avoid conflicts * Make travis happy by updating ava snapshots * Fix sha1 to sha512 flipping per npm 5.3.0 issue
I struggled to get caddy to work. I ended up using http-server instead ( |
Thank you so much @devinrhode2 , after a long day searching finally |
Any way to do it or is it planned?
The text was updated successfully, but these errors were encountered: